devops: start releasing from Github Actions #1890
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 patch: - removes releasing from Travis CI - sets up a new GH Action that releases @next version from tip-of-tree Once this GH Action proves to be working, we'll setup a `publish_release.yml` workflow that will be triggered only by **release** github events and that will publish released version with `LATEST` tag. NOTE: this workflow does not actually run publishing - we're doing `--dry-run` for now to see how it works in `//utils/publish_all_packages.sh`.
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 patch:
Once this GH Action proves to be working, we'll setup a
publish_release.ymlworkflow that will be triggered only by release github events
and that will publish released version with
LATESTtag.NOTE: this workflow does not actually run publishing - we're doing
--dry-runfor now to see how it works in//utils/publish_all_packages.sh.