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
This is a tracking issue for things that could change in v10:
afterAddToChangelog
afterChangelog
canary
next
The text was updated successfully, but these errors were encountered:
🚀 Issue was released in v10.0.0 🚀
v10.0.0
Sorry, something went wrong.
No branches or pull requests
This is a tracking issue for things that could change in v10:
Call canary/next hooks even for dry-runs, plugins handle it, enables better --dry-run and --quiet output. bad coderenameafterAddToChangelog
toafterChangelog
since a changelog might not be committedmake renderChangelogLine waterfall not have to return tuple, it can just return the linegit reset aftercanary
andnext
hooks. These should not leave any traces of the last published version other than tags fornext
The text was updated successfully, but these errors were encountered: