chore/GHA release infrastructure#54
Merged
blast-hardcheese merged 2 commits intomainfrom Jul 24, 2024
Merged
Conversation
blast-hardcheese
requested review from
a team and
Monkatraz
and removed request for
a team
blast-hardcheese
added a commit
that referenced
this pull request
Jul 25, 2024
Why === Follow-up to #54, enable `release-drafter`. What changed ============ Adding the release-drafter action to consume the configuration and curate release drafts on every merge to the default branch. Test plan ========= When this PR gets merged, do we get a new release draft?
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Why
Similar to replit-py and replit-object-storage, we should have a Release-oriented release process. This gives increased visibility into how our libraries change from version to version, as well as offering consistency for maintainers releasing changes.
What changed
release-drafterconfig. This must be done before adding the workflow in a second PR, since the workflow always accesses the default branch for its configuration.python-publishaction that publishes an update any time a new release is cutTest plan
Once merged, it should be possible to trigger the workflow to publish a new version of the library via workflow_dispatch or creating a release