devops: introduce release publishing workflow #1894
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
This workflow is based on the Github Actions docs: [publishing node.js packages](https://help.github.com/en/actions/language-and-framework-guides/publishing-nodejs-packages) It should be triggered once we create a github release. It's unclear how to test this workflow, so I tried to re-use as much code from `publish_canary.yml` as possible.
|
Is there a short description of how to use this one? I also wonder where does the npm secret come from? |
It should be automatically triggered once we publish github release
This could be found in |
dgozman
approved these changes
Apr 21, 2020
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.
This workflow is based on the Github Actions docs: publishing node.js
packages
It should be triggered once we create a github release.
It's unclear how to test this workflow, so I tried to re-use as much
code from
publish_canary.ymlas possible.