-
Notifications
You must be signed in to change notification settings - Fork 33
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: add release scripts #93
Conversation
The current 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. |
https://app.circleci.com/pipelines/github/salesforce/eslint-plugin-lwc/281/workflows/a3b90f6a-e1a7-4823-9313-7d8f5e5afa24/jobs/384 for sample dry run of the deploy job. |
With the CircleCI script, our general release process should now be:
CircleCI should now handle the publish. |
Work to automate changelog generation and release notes will be done in a separate PR. |
package.json
Outdated
"test": "nyc mocha" | ||
"test": "nyc mocha", | ||
"release:version": "npm version", | ||
"release:publish:ci": "npm publish --registry=https://registry.npmjs.org --dry-run" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will remove the --dry-run
tag AFTER review for safety.
One step closer to a 1-button release process.
The remaining work involves git automation around branch protection, pushing the actual changes to the remote, and changelog generation.