Automate Tarball Release and Publish to Conda-Forge #136
Conversation
This file contains hidden or 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
…e meta.yamlv1.2.6
…e meta.yamlv1.2.7
…e meta.yamlv1.2.8
…e meta.yamlv1.2.10
…e meta.yamlv1.2.11
…e meta.yamlv1.2.13
Signed-off-by: Hudson Xing <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of changes:
This PR introduces automation for the release workflow of the SageMaker Code Editor tarball, as well as publishing to conda-forge:
The package and tarball are now versioned according to a defined versioning strategy.
Tarball generation is triggered automatically upon creation of a version tag via GitHub Actions.
A new GitHub Action is added to create a pull request for conda-forge feedstock, updating it with the latest tarball version.
The design documentation is updated to describe the versioning strategy, tarball generation, and conda-forge update process.
This automation streamlines the release cycle and minimizes manual intervention for both artifact generation and conda-forge publication.