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
package.json
Hi!
I use bumpp to raise the version of my package.
I used conventional-changelog and standard-version for generating changelogs before.
It worked according to the following algorithm:
bumpp
standard-version
conventional-changelog
Example of package.json:
{ "scripts": { "release": "pnpm release:check && pnpm release:version && pnpm release:publish", "release:changelog": "standard-version --infile changelog.md --same-file --skip.bump --skip.commit --skip.tag", "release:check": "pnpm test && pnpm build", "release:publish": "clean-publish", "release:version": "bumpp package.json --execute=\"pnpm release:changelog && git add changelog.md\" --commit \"build: publish v%s\" --tag --all", } }
I would like to be able to generate changelogs without creating a tag and getting a new version from package.json
The text was updated successfully, but these errors were encountered:
Hi. Would using --bump --no-tag --no-commit make sense to you?
--bump --no-tag --no-commit
Sorry, something went wrong.
No branches or pull requests
Describe the feature
Hi!
I use bumpp to raise the version of my package.
I used conventional-changelog and standard-version for generating changelogs before.
It worked according to the following algorithm:
bumpp
updates the version inpackage.json
standard-version
orconventional-changelog
generate the changelog from latest version tag to version frompackage.json
bumpp
create commit and tag with new version and push to origin repoExample of
package.json
:I would like to be able to generate changelogs without creating a tag and getting a new version from
package.json
Additional information
The text was updated successfully, but these errors were encountered: