feat: split release workflow into prepare and publish#301
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #301 +/- ##
=======================================
Coverage ? 91.09%
=======================================
Files ? 35
Lines ? 3741
Branches ? 566
=======================================
Hits ? 3408
Misses ? 182
Partials ? 151
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
avi-alpert
approved these changes
Mar 9, 2026
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
4 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.
Issue #, if available: #282
Description of changes:
Problem
The current release.yml runs version bump, build, approval, and PyPI publish in a single pipeline. The environment approval gate is not tied to PR approval, so the package can be published from an unmerged branch —
meaning main doesn't reflect what's on PyPI, and tags point to the wrong commit.
Solution
Split into two workflows with the PR merge as a hard gate:
The old release.yml is renamed to legacy-release.yml as a fallback until the new workflows are verified in production.
Testing
Tested on personal fork (Hweinstock/bedrock-agentcore-sdk-python):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.