Open mohijalili opened 1 month ago
Hey @edbzn , Can you help me out?
Hey, @mohijalili have you tried creating a light weight “last-release” tag based on a specific commit and pushing it from your local to your remote before running your workflow?
For example, create a tag based off the commit you want to start from on your local “git tag last-release COMMIT_HASH”. Then, push it to your remote “git push origin last-release” and start your release on GitHub.
Side note, you should remove the baseBranch, allowEmptyRelease, and dry-run flags from your version job in your workflow before running if you want to create a release.
Hey, @mohijalili have you tried creating a light weight “last-release” tag based on a specific commit and pushing it from your local to your remote before running your workflow?
For example, create a tag based off the commit you want to start from on your local “git tag last-release COMMIT_HASH”. Then, push it to your remote “git push origin last-release” and start your release on GitHub.
Side note, you should remove the baseBranch, allowEmptyRelease, and dry-run flags from your version job in your workflow before running if you want to create a release.
@christiankaseburg Yeah, I tried it and, like you said, I ran into two different errors while setting up semver. (you can find it in the initial description) Can you explain why I should remove baseBranch
, allowEmptyRelease
, and dry-run
?
Description
I am encountering an issue when running the
semver
for the first time and subsequently when triggered by GitHub Actions. Initially, I receive the following message:After removing the tags and running the action again, I encounter this error:
GitHub Action Configuration
Below is the configuration of my GitHub Action for semantic release:
Each project has the following config:
Additional Context