Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@jye-sf
Copy link
Contributor

@jye-sf jye-sf commented Apr 12, 2022

Standardize the naming for our release scripts:

yarn release -> full service release
yarn release:version -> update the version
yarn release:publish -> publish the project

@jye-sf
Copy link
Contributor Author

jye-sf commented Apr 12, 2022

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?

@jye-sf
Copy link
Contributor Author

jye-sf commented Apr 12, 2022

Assuming we want version updates, the general release process for our repos will be:

// Version update
yarn release:version

// github related tasks
git push origin <branch>
git push origin <tag>

// Publish
yarn release:publish

Github related tasks require unlocking and re-locking branch protections. Will look into having CircleCI handle that.

@jye-sf
Copy link
Contributor Author

jye-sf commented Apr 13, 2022

Will spend tomorrow refactoring all the other repos into publish.js with a CI check if the rest of the review looks good.

@jye-sf jye-sf closed this Apr 14, 2022
@jye-sf jye-sf reopened this Apr 14, 2022
@jye-sf jye-sf merged commit 0b27042 into master Apr 14, 2022
@jye-sf jye-sf deleted the jye/streamline-release branch April 14, 2022 22:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants