feat(v2): add automated canary releases #3827
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Deploy preview for docusaurus-2 ready! Built with commit 51d1517 |
|
⚡️ Lighthouse report for the changes in this PR:
Lighthouse ran on https://deploy-preview-3827--docusaurus-2.netlify.app/classic/ |
|
Size Change: +16 B (0%) Total Size: 156 kB ℹ️ View Unchanged
|
slorber
commented
Nov 26, 2020
| @@ -32,6 +32,9 @@ | |||
| "crowdin:upload:v2": "crowdin upload sources --config ./crowdin-v2.yaml", | |||
| "crowdin:uploadTranslations:v2": "crowdin upload translations --config ./crowdin-v2.yaml", | |||
| "crowdin:download:v2": "crowdin download --config ./crowdin-v2.yaml", | |||
| "canary": "yarn canary:bumpVersion && yarn canary:publish", | |||
| "canary:bumpVersion": "yarn lerna version 2.0.0-alpha.`git rev-parse --short HEAD` --exact --no-push --yes", | |||
| "canary:publish": "yarn lerna publish from-package --dist-tag canary --yes", | |||
There was a problem hiding this comment.
Notes:
- tried to use
lerna publish --canarybut wasn't able to make it work, as it seems to refuse to publish unchanged packages, and to generate a good version name (probably because we already use alpha.patch) from-packageshould be convenient, as if we try to publish twice the same version, it will just avoid to publish packages that are already published, instead of failing due to trying to publish twice the same version (ex: we restart the CI on same commit: it should still work)
slorber
changed the title
slorber
added
pr: maintenance
|
The NPM_AUTH_TOKEN has been added as GH actions env variable, for publish permission to NPM. Let's merge and hope it works! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
Make new fixes accessible to power users as soon as they get merged, by publishing a npm version under the "canary" dist tag.