Skip to content

ci: migrate 2 of 3 release-npm.yml jobs to smithy self-hosted runners#2

Open
avrabe wants to merge 1 commit intomainfrom
smithy-migration
Open

ci: migrate 2 of 3 release-npm.yml jobs to smithy self-hosted runners#2
avrabe wants to merge 1 commit intomainfrom
smithy-migration

Conversation

@avrabe
Copy link
Copy Markdown
Contributor

@avrabe avrabe commented May 3, 2026

Summary

The repository has only one workflow (release-npm.yml, triggered on
release publish or workflow_dispatch). Two of its three jobs
(publish-npm, build-platform-packages) only need Node, jq, and
the GitHub CLI — well within the 4 G light smithy class. They move
to smithy. The third job (build-binaries) is a four-OS release
matrix and stays on hosted because smithy is Linux-only.

Coverage

Job New runner Class
publish-npm smithy light
build-platform-packages smithy light

Stays on ubuntu-latest

Job Reason
build-binaries Cross-OS release matrix (ubuntu-latest, macos-latest, macos-14, windows-latest). Smithy is Linux-only.

Workarounds applied

None — both migrated jobs are clean runs-on: swaps. They use only
actions/setup-node, npm publish, jq, and gh release — none of
which need sudo, apt, or any pattern called out in the playbook.

Test plan

  • Next published release triggers the workflow; publish-npm and
    build-platform-packages land on light smithy runners within
    seconds (no GitHub queue).
  • Both jobs succeed end-to-end (npm publish against
    registry.npmjs.org).
  • build-binaries still runs across the four release-target OSes
    on ubuntu-latest / macos-* / windows-latest as before.

Rollback

Revert this commit. Both migrated jobs return to ubuntu-latest and
the next release run uses GitHub-hosted compute.

  light        publish-npm, build-platform-packages

Stays on ubuntu-latest:
  - build-binaries  cross-OS release matrix (linux/macos/macos-14/win)

The two npm-publish jobs only run `npm publish` + jq + gh CLI, which
is well within the 4 G `light` budget.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant