smooth-release
smooth-release copied to clipboard
buildo
Replacement for `npm version` and `npm publish` with validations and CHANGELOG.md + GitHub release generation
If 2-factor authentication is required to publish on NPM, smooth-release fails on the `npm publish` step. Running that step separately instead works, prompting for the OTP. It would be nice...
## description The package version is updated in `package.json` but not in `package-lock.json`. Both files are updated locally, but only `package.json` is committed. ## how to reproduce - {optional: describe...
## requirements this issue is the outcome of a discussion on this PR: https://github.com/buildo/smooth-release/pull/96#event-1103811044 Right now, issues without known labels, are always treated as "features". Some users may prefer to...
## description When passing version/increase level as argument, to override the npm-version task behaviour, smooth-release still asks "Do you want to run the "npm-version" task and increase the version of...
Right now, if a command in the middle of the process prompts the user (like `git push` asking for credentials or a confirm to push on master), there is no...
## requirements We may consider this: Optionally post a comment on every newly released issue to notify users it's now available. Also write the library's version it was release with...
## requirements Some complex repos (ex: `npm`) keep supporting old versions. This is a problem if you want to use `smooth-release` as the breaking logic considers only the breaking issues...
`smooth-release` should pause between `UPDATE CHANGELOG` and `COMMIT AND PUSH CHANGES`, so you can inspect the ChangeLog that was generated locally, before it is pushed to GitHub.