Replies: 2 comments 4 replies
-
if the previous tag does not exist in the branch you are releasing from, it will not be found by semantic-release. the tag needs to exist and it need to be in the history of the branch you are releasing from. if it is there properly, semantic-release does work. also, if you are creating tags locally in an attempt to resolve an issue with missing tags, be sure you are actually pushing the tags to your remote. that normally requires a |
Beta Was this translation helpful? Give feedback.
-
EDIT: The below solution worked only once. I was able to solve this by doing these steps –
|
Beta Was this translation helpful? Give feedback.
-
Many months ago, I migrated the default branch of my repo from
master
tomain
, and ever since then, semantic-release has never been the same.I keep going back to the troubleshooting guide and do all the steps, but the release process is now permanently broken and has become unreliable when applying manual fixes.
Example workflow run that reports the wrong version – https://github.com/paambaati/codeclimate-action/actions/runs/4905711649/jobs/8759663416
The dry run keeps picking up the last commit as
v3.2.0
when in fact,v4.0.0
was released by semantic-release (see https://github.com/paambaati/codeclimate-action/actions/runs/4777730343/jobs/8493671186). I've also followed the troubleshooting guide to recreate my tags and ref notes, with no luck.EDIT: Additional information as I continue to debug this –
Looks like
git tag --merged main
returns only a few tags.The above steps no longer work either, and I'm at my wits' end. I'd really appreciate if someone can help fix this for good.
Beta Was this translation helpful? Give feedback.
All reactions