shipjs
shipjs copied to clipboard
Take control of what is going to be your next release.
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [change-case](https://togithub.com/blakeembrey/change-case) | [`4.1.1` -> `4.1.2`](https://renovatebot.com/diffs/npm/change-case/4.1.1/4.1.2) | [](https://docs.renovatebot.com/merge-confidence/)...
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [jest-watch-typeahead](https://togithub.com/jest-community/jest-watch-typeahead) | [`0.6.0` -> `0.6.5`](https://renovatebot.com/diffs/npm/jest-watch-typeahead/0.6.0/0.6.5) | [](https://docs.renovatebot.com/merge-confidence/)...
[](https://renovatebot.com) This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [patch-package](https://togithub.com/ds300/patch-package) | dependencies | pin | [`^6.2.2` -> `6.2.2`](https://renovatebot.com/diffs/npm/patch-package/6.2.2/6.2.2) | |...
[](https://renovatebot.com) This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [json](https://togithub.com/trentm/json) | [`9.0.6` -> `10.0.0`](https://renovatebot.com/diffs/npm/json/9.0.6/10.0.0) | [](https://docs.renovatebot.com/merge-confidence/)...
**Is your feature request related to a problem? Please describe.** What I'm trying to achieve is setting the `next` and `latest` tags based on branches. I want ship.js to trigger...
**Is your feature request related to a problem? Please describe.** When we run `shipjs prepare` at local, .env is needed. But Shipjs's log when run command `shipjs setup` does not...
**Describe the bug** A clear and concise description of what the bug is. with only one commit, e.g. `feat: init`, it says: ``` › Getting a revision range for this...
When using `toReleaseBranch` strategy, there can be a possibility that the working branch is protected. It means after release, when Ship.js tries to merge the release branch back to the...
**Is your feature request related to a problem? Please describe.** When setting your `mergeStrategy` to ` toReleaseBranch`, Ship.js creates a merge commit in the `develop` branch (merges `master` back). This...