Skip to content

ci: use dedicated runners for release publishing #2267

Description

@aidandaly24

Description

Follow up on #2259. The release-publish workflow on refactor is now allowlisted for the aws-release-4-core runner group, but its check-release and publish jobs still request ubuntu-latest.

Expected Change

  • Move both jobs to aws-release-4-core, matching release preparation.
  • Preserve the push trigger, release-PR checks, commit pinning, permissions, and verification matrix.
  • Document that the publishing workflow's allowlist currently covers refactor, not main. After the file lands on main, its runner-group pin must be added before changing the branch filter.

This does not require publishing a package or dispatching a release for validation.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions