We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
My semantic release config:
"release": { "plugins": [ "@semantic-release/commit-analyzer", "@semantic-release/release-notes-generator", "@semantic-release/github", "@semantic-release/npm", "@semantic-release/git" ], "prepare": [ "@semantic-release/npm", { "path": "@semantic-release/git", "assets": [ "package.json" ], "message": "chore(app release): ${nextRelease.name} [skip required checks]\n\n${nextRelease.notes}" } ], "branches": [ { "name": "main", "prerelease": false, "channel": "prod" }, { "name": "dev", "prerelease": "dev", "channel": "dev" }, { "name": "staging", "prerelease": "staging", "channel": "staging" } ] },
semantic-release version 19.0.2
semantic-release
I've noticed that if the PR mentions the issue like this:
- Closes https://github.com/some-org/some-repo/issues/123
Semantic release doesn't label the issue (it usually adds released on @channel label), only the PR. However if in the PR I write:
released on @channel
Closes #123
Then it works. I'm guessing it can't parse the issue number from the link?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
My semantic release config:
semantic-release
version 19.0.2I've noticed that if the PR mentions the issue like this:
- Closes https://github.com/some-org/some-repo/issues/123
Semantic release doesn't label the issue (it usually adds
released on @channel
label), only the PR. However if in the PR I write:Closes #123
Then it works. I'm guessing it can't parse the issue number from the link?
The text was updated successfully, but these errors were encountered: