-
Notifications
You must be signed in to change notification settings - Fork 14
chore: standardize release script #57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
I've noticed we rarely update the version on this project, so I'm assuming we're publishing with the same version. Is that intentional, or should I be adding a version update into the process? |
|
Assuming we want version updates, the general release process for our repos will be: Github related tasks require unlocking and re-locking branch protections. Will look into having CircleCI handle that. |
|
Will spend tomorrow refactoring all the other repos into |
Standardize the naming for our release scripts:
yarn release -> full service release
yarn release:version -> update the version
yarn release:publish -> publish the project