ci: use dedicated release runners - #645
Open
aidandaly24 wants to merge 1 commit into
Open
Conversation
agentcore-devx-automation
Bot
added
the
claude-security-reviewing
Contributor
|
Claude Security Review: no high-confidence findings. (run) |
agentcore-devx-automation
Bot
removed
the
claude-security-reviewing
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #645 +/- ##
=======================================
Coverage ? 88.92%
=======================================
Files ? 120
Lines ? 10202
Branches ? 1563
=======================================
Hits ? 9072
Misses ? 749
Partials ? 381
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
tejaskash
approved these changes
Aug 20, 2026
tejaskash
left a comment
tejaskash
left a comment
Contributor
There was a problem hiding this comment.
Reviewed the release-runner changes. Release preparation and validation move consistently to the dedicated runner, while the pull-request-triggered publish workflow remains on the shared runner.
notgitika
approved these changes
Aug 20, 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.
Summary
Moves the manually triggered release preparation workflow to the dedicated
aws-release-4-coreGitHub-hosted runner group. This prevents release preparation from waiting behind the sharedubuntu-latestpool.The
release-publish.ymlworkflow is intentionally unchanged because it is triggered bypull_request: closed; the dedicated runner is restricted to release workflows triggered byworkflow_dispatchor pushes tomain.Testing
Parsed both release workflows as YAML, verified every job in
release-prepare.ymlusesaws-release-4-core, and verified the pull-request-triggered publish workflow does not use the dedicated runner. Source tests were not run because this change only updates workflow runner labels.Security
No permissions, triggers, dependencies, or secrets changed.