ci: use dedicated release runners - #2052
Merged
Merged
Conversation
github-actions
Bot
added
size/xs
agentcore-devx-automation
Bot
added
the
claude-security-reviewing
Contributor
Package TarballHow to installgh release download pr-2052-tarball --repo aws/agentcore-cli --pattern "*.tgz" --dir /tmp/pr-tarball
npm install -g /tmp/pr-tarball/aws-agentcore-0.27.1.tgz |
Contributor
|
Claude Security Review: no high-confidence findings. (run) |
agentcore-devx-automation
Bot
removed
the
claude-security-reviewing
github-actions
Bot
removed
the
agentcore-harness-reviewing
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. Both release workflows remain manually triggered, the runner migration is consistent across all jobs, and the existing shared-runner/security boundaries are preserved.
jariy17
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.
Description
Moves both release workflows to the dedicated
aws-release-4-coreGitHub-hosted runner group. This keeps release publishing and provenance on GitHub Actions without competing with the sharedubuntu-latestpool.Both workflows remain manually triggered with
workflow_dispatch; no pull-request-triggered workflow can target the release runner.Related Issue
N/A - operational CI capacity change.
Documentation PR
N/A
Type of Change
Testing
How have you tested the change?
npm run test:unitandnpm run test:integnpm run typechecknpm run lintsrc/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsaws-release-4-corepull_requesttriggerSource tests were not run because this change only updates workflow runner labels.
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.