Skip to content
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

chore: standardize release script #270

Merged
merged 8 commits into from Apr 18, 2022
Merged

chore: standardize release script #270

merged 8 commits into from Apr 18, 2022

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?

@nolanlawson
Copy link
Contributor

@jye-sf I think we just haven't released in a while because there was nothing to change. When we do a release, we should bump the version.

package.json Outdated Show resolved Hide resolved
@@ -27,7 +27,9 @@
"lint": "eslint src/ tests/",
"format": "prettier --write '**/*.{js,json,md,html,css}'",
"format:check": "prettier --check '**/*.{js,json,md,html,css}'",
"release": "npm publish --access public",
"release": "yarn release:publish",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Full service command will require a script that can read args (for version upgrade) and proper permissions to merge into master. Keeping this script as-is until we have that functionality.

@jye-sf jye-sf requested a review from nolanlawson April 13, 2022 04:53
package.json Outdated
"release": "yarn release:publish",
"release:version": "npm version",
"release:publish": "npm publish --access public --registry=https://registry.npmjs.org",
"release:publish:ci": "npm publish --access public --registry=https://registry.npmjs.org --dry-run",
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will remove --dry-run after review for safety.

executors:
node:
docker:
- image: circleci/node:14
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- image: circleci/node:14
- image: cimg/node:14.19.1

Comment on lines 30 to 32
keys:
- v1-yarn-deps-{{ checksum "yarn.lock" }}
- v1-yarn-deps-
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
keys:
- v1-yarn-deps-{{ checksum "yarn.lock" }}
- v1-yarn-deps-
key: v1-yarn-deps-{{ checksum "yarn.lock" }}

@jye-sf jye-sf merged commit 4c13a88 into master Apr 18, 2022
@jye-sf jye-sf deleted the jye/streamline-release branch April 18, 2022 07:31
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.

None yet

2 participants