One of the main goals we had when building auto was to ease the introduction to automated releases through using pull request labels.
Publishing canary versions comes with some security risks. If your project is private you have nothing to worry about, but if your project is open source there are some security holes.
Sometimes you are working on a big feature and you know it will require a lot of changes. These types of pull requests can be a nightmare to review. Taking in all the changes at once can be overwhelming. It makes it easy to miss smaller mistakes and can make it hard to guess the intent of the changes. Multiple features, bug fixes, or even breaking changes may make up this large PR.
auto
makes releasing your code a breeze. Instead of manually calculating a version and doing your whole release process manually, auto
takes care of it for you.
We are excited to announce the release of auto
8.0.0.
This release brings a new command next
, a new use for shipit
, more powerful label configuration, and more.
I've been a front-end engineer at Intuit in San Diego for the past three years. As one of three members of Intuit's Player team, we are responsible for delivering a JavaScript framework dedicated to rendering most of a user's experience in TurboTax. We end up releasing a lot of code, usually React components, quite frequently to our internal node package manager (npm) instance. It's not uncommon for us to hit double-digit releases in a single day. This means lots of version bumps, release notes, changelogs, Jira tickets, Slack announcements, and all the other goodies that come with communicating to dependent teams, that their bug is now fixed, or a new feature is ready for them to use. While none of these steps are intrinsically difficult, the time commitment adds up quickly, so we wrote auto: a tool to auto-generate releases based on semantic version labels.