Replies: 2 comments 1 reply
-
I have an interesting observation about this behavior. The last version was detected properly before I explicitly did the following:
However, then the current branch name test done by semantic-release fails. (We only bump the version when in a semantic release output with no
|
Beta Was this translation helpful? Give feedback.
-
it looks like your existing tags are not prefixed with
i dont have an explanation for this and would expect this to fail in the same way if there is no local tag of |
Beta Was this translation helpful? Give feedback.
-
We have an Azure pipeline that builds an IPA for a React Native app on a MacOS build agent. I am trying to get the
npm run release
command to work in this pipeline, so we do not have to bump the version manually prior to running the pipeline. The pipeline does not checkout by the branch, so I have to do it manually here. I have tried fetching the tags, but that does not help. I can see that the previous build's version tags are present in the local git cache.The next version should be 4.2.1, but semantic-release, when run from a pipeline, thinks it should be 1.0.0. From my local system, it correctly increments the version to 4.2.1.
What am I missing in the build environment that is preventing semantic-release from detecting the previous release tag?
semantic-release config in package.json:
Azure configuration:
Build output from this step:
Beta Was this translation helpful? Give feedback.
All reactions