This repository has been archived by the owner on Oct 1, 2024. It is now read-only.
Enable self service dev releases #1278
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
ismail-syed
changed the title
donnielrt
reviewed
Feb 12, 2020
|
|
||
| ### Step 1 - publish a beta(s) | ||
|
|
||
| - In your branch, run `yarn run release-beta`. Lerna will launch it's CLI to select a version for the changed pacakges. Select the `Custom` option and enter a version with an appended `-beta.X` (eg. `0.29.10-my-feature-beta.1`) |
ismail-syed
force-pushed
the
self-server-beta-releases
branch
3 times, most recently
from
3ca4118 to
6ee8b0a
Compare
marutypes
approved these changes
Feb 13, 2020
helloneele
reviewed
Feb 13, 2020
|
|
||
| - In your branch, run `yarn run release-beta`. Lerna will launch it's CLI to select a version for the changed packages. Select the `Custom` option and enter a version with an appended `-beta.X` (eg. `0.29.10-my-feature-beta.1`) | ||
| - Push your branch to Github with the newly created tags using `git push origin <branch> --follow-tags` | ||
| - Create a temporary stack in Shipit that points to your beta branch |
There was a problem hiding this comment.
This step could be more explicit
A note about replacing the environment with beta-test-<branch> would be good.
helloneele
reviewed
Feb 13, 2020
| - In your branch, run `yarn run release-beta`. Lerna will launch it's CLI to select a version for the changed packages. Select the `Custom` option and enter a version with an appended `-beta.X` (eg. `0.29.10-my-feature-beta.1`) | ||
| - Push your branch to Github with the newly created tags using `git push origin <branch> --follow-tags` | ||
| - Create a temporary stack in Shipit that points to your beta branch | ||
| - Hit the deploy button in Shipit to publish your beta to npm |
There was a problem hiding this comment.
Hit the deploy button on your Publish commit in Shipit to publish your beta to npm
helloneele
reviewed
Feb 13, 2020
|
|
||
| ### Step 1 - publish a beta(s) | ||
|
|
||
| - In your branch, run `yarn run release-beta`. Lerna will launch it's CLI to select a version for the changed packages. Select the `Custom` option and enter a version with an appended `-beta.X` (eg. `0.29.10-my-feature-beta.1`) |
There was a problem hiding this comment.
This could maybe have some instructions on what to do when a package change causes other packages to be bumped as well. 🙂
helloneele
approved these changes
Feb 13, 2020
ismail-syed
changed the title
ismail-syed
force-pushed
the
self-server-beta-releases
branch
from
75a837b to
4b44145
Compare
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Allow Shopify developers to self serve dev releases for testing and hot fixes. See docs