Manage semver-like formats

[fastify]

Manage semver-like formats

[simoneb]

@Eomm can you do a manual release of the action? We'll have to wait until next week before publishing this action using release automation, because the current version is not capable of auto updating if we create the non-semver tags

[simoneb]

and it should also keep working with submodules. see #98

[nuragic]

One approach is the one mentioned above by @Eomm; another approach would be to use the valid SemVer number, which is in this case 2.3.0... would be that possible? It seems that we have that information in the pull requests opened by dependabot, e.g.

We're extracting the 2.3 from the title?

[simoneb]

We're extracting the 2.3 from the title?

yes. I think the approach is to use coerce / loose options from the semver library

[nuragic]

What I'm saying is that IMHO the right thing to do would be to have the valid SemVer number even in the title, e.g.

chore(deps): bump actions/setup-node from 2.4.1 to 2.5.0
nearform-actions/optic-release-automation-action#15

[simoneb]

we can't, we're not creating those PRs, dependabot is

[nuragic]

Yeah of course hehe I know but there's no way to fix that by changing some config here?

https://github.com/fastify/github-action-merge-dependabot/blob/main/.github/dependabot.yml

[simoneb]

no

[Eomm]

Yes, I have checked the main dist folder and it is all aligned.

Publishing...

[austins]

I'm having an issue where the action still merges a major release even if the target is set to minor.

For example, React v17.0.2 to v18.0.0 still gets merged.

    automerge:
        needs: analyze
        runs-on: ubuntu-latest
        permissions:
            pull-requests: write
            contents: write
        if: ${{ github.event_name == 'pull_request' }}
        steps:
            -   uses: fastify/github-action-merge-dependabot@v3
                with:
                    github-token: ${{ secrets.GITHUB_TOKEN }}
                    target: minor

Example PR: austins/smoothnanners-web#17