chore(stepsecurity): update workflows to use custom hosted runners with built-in StepSecurity#133
Merged
ali-kafel merged 1 commit intocirclefin:masterfrom Dec 10, 2025
Conversation
…th built-in StepSecurity
circle-ops-ci
approved these changes
Dec 9, 2025
circle-ops-ci
left a comment
circle-ops-ci
left a comment
There was a problem hiding this comment.
Automated Repo-Updater Approval #1
ashutosh-ukey
pushed a commit
that referenced
this pull request
Mar 18, 2026
🤖 I have created a release *beep* *boop* --- ## [2.10.0](v2.9.0...v2.10.0) (2026-03-18) ### Features * sync SDK to OpenAPI doc v2.11.1 ([#117](#117)) ([d56319f](d56319f)) * sync SDK to OpenAPI doc v2.12.0 ([#118](#118)) ([d2dd9c1](d2dd9c1)) * sync SDK to OpenAPI doc v2.14.0 ([#124](#124)) ([d64938e](d64938e)) * sync SDK to OpenAPI doc v2.15.0 ([#125](#125)) ([5b34ebb](5b34ebb)) * sync SDK to OpenAPI doc v2.16.0 ([#139](#139)) ([0ceb254](0ceb254)) ### Miscellaneous Chores * apply security best practices and onboard stepsecurity ([#131](#131)) ([357d2fe](357d2fe)) * **deps:** bump action versions to use node 20 ([#113](#113)) ([fe5002d](fe5002d)) * **stepsecurity:** update workflows to use custom hosted runners with built-in StepSecurity ([#133](#133)) ([40ee83f](40ee83f)) ### Continuous Integration * fix shared release-please workflow bug ([#136](#136)) ([d23c2ec](d23c2ec)) * fix shared release-please workflow bug pt 2 ([#137](#137)) ([12f2664](12f2664)) * use public shared Circle workflows repo ([#121](#121)) ([093fd41](093fd41)) * use shared release-please workflow ([#120](#120)) ([4bb61fb](4bb61fb)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
nexx88
pushed a commit
that referenced
this pull request
Mar 20, 2026
## Summary Restore `id-token: write` in the reusable npm publish workflow so AWS OIDC auth works during publish ### Why - the publish pipeline is failing in `Configure AWS Credentials` before `npm publish` - `aws-actions/configure-aws-credentials` is using `role-to-assume`, which requires a GitHub OIDC token - the workflow only grants `contents: read`, so the job cannot mint that token ## Details ### Regression Context - `id-token: write` was originally added in [`ffcaf51`](ffcaf51) (`fix: allow OIDC token in publish pipeline (#25)`) - it was removed in [`40ee83f`](40ee83f) (`chore(stepsecurity): update workflows to use custom hosted runners with built-in StepSecurity (#133)`) - that regression stayed hidden until [`27f4efe`](27f4efe) (`ci: fix release-please wiring (#140)`) fixed release gating and caused `npm-publish` to run again ## Validation - reviewed failed run [`23300901189`](https://github.com/circlefin/circle-nodejs-sdk/actions/runs/23300901189) and failing job [`67761702334`](https://github.com/circlefin/circle-nodejs-sdk/actions/runs/23300901189/job/67761702334) - confirmed the job fails in `Configure AWS Credentials` with the log: `Did you mean to set the id-token permission?`
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
3 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
This PR updates GitHub Actions workflows to use custom hosted runners that have StepSecurity built-in, removing the need for the explicit StepSecurity harden-runner action.
What Changed
Purpose
Our custom hosted runners (github-hosted-small) now have StepSecurity built-in at the runner level, so we no longer need to add it as an explicit step in each workflow. This simplifies our workflows while maintaining the same security posture.
Testing