Version Not Incremented After Release #1951
Unanswered
vozeldr
asked this question in
Configuration
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to use this semantic-release tool to automate the generation and publication of a REST API client. The REST API lives in the same repository as the client. I am using nswag to auto-generate the API client based on the swagger generated from the API project. That bit is all working.
When changes are made to the REST API that require updates to the client library, I want my github action workflow to trigger semantic-release to generate and publish a new npm package to github packages. That seemed to be working and changes tagged with
chore
ordoc
weren't generating new beta releases into the develop branch whereas changes tagged withfeat
were.I have the following configuration in my
package.json
for release channels:Everything seemed like it was working well at first, but I didn't notice the version being published on the beta channel did not increment after the 1.0.0.0 version was released by a merge into master. The next time I attempted to merge into master, I got the error that 1.0.0.0 already exists.
I'm fairly certain I've read through all of the documentation (although I don't fully understand it all) and I can't seem to find how to use your tool for this simple workflow. Can someone please help me with this configuration? The goal is to really never have to touch this going forward. When changes are made to the REST API, a new version of the API client will be generated and published automatically. I don't want to have to mess with custom branch naming and maintaining the package.json file... set it and forget it.
Beta Was this translation helpful? Give feedback.
All reactions