Closed marcysutton closed 7 years ago
I don't think we'll need standard-version. We'll have that covered by our release tool
Ok, I've reset this branch so it only includes the contributing.md file without the release steps. We can add those instructions later once the process with attest-master gets nailed down.
Manually updating the version is super error-prone, and it already bit me once with axe-cli (I meant to release 1.1.0, yet somehow it got updated to 1.1.1).
We should use the same process as axe-core for this instead of doing it by hand. Since I'm the one typically releasing our open source modules, I'd really prefer a single process. The only difference with axe-cli is it doesn't use sri-history. I know we're moving to attest-master for Bitbucket repos, but this will give us a workable solution for Github now.
I guess to go along with this change: we should stop incrementing the version by hand until we're ready to release. It's confusing to go hunt it down every time when I'm releasing code.