Take control of what is going to be your next release.
Take control of what is going to be your next release.
https://community.algolia.com/shipjs/
Running the following command will guide you to set it up interactively.
npx shipjs setup
This interactive CLI will help you install Ship.js into your package and create a tailored config file for your project.
Coding is fun, debugging and testing are okay, but releasing is NOT.
When releasing, you go through something like the following:
package.json
npm run build && npm publish
)In Ship.js, the release process consists of three parts.
shipjs prepare
)Run shipjs prepare
and it will briefly do the following:
It takes less than a couple of minutes.
When you think it's ready to release, merge the PR.
shipjs trigger
)Run shipjs trigger
and it will briefly do the following:
You can manually run shipjs trigger
on the base branch after the PR is merged.
However you can also configure your CI service(e.g. CircleCI) to do this for you. It means the longest process is on the CI service asynchronously, not occupying your working environment.
Let's move on to the guide.
Or, you can watch this video if you prefer.
semantic-release is a tool for fully automated version management and package publishing
.
Ship.js gives you more control over the release process. Ship.js automatically creates a PR before publishing every release, so that you can:
Thanks goes to these wonderful people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Show the world you're using Ship.js
[![deploy](https://img.shields.io/badge/deploy-π³%20Ship.js-blue?style=flat)](https://github.com/algolia/shipjs)
<a title="deploy" href="https://github.com/algolia/shipjs" rel="nofollow">
<img src="https://img.shields.io/badge/deploy-π³%20Ship.js-blue?style=flat" />
</a>