Repository navigation
fix(aws.js): install actions/runner 2.338.0 - #2
Merged
Merged
Conversation
GitHub has rejected runner registrations below 2.329.0 since 2026-09-29, so instances started with 2.313.0 never come online and the jobs waiting for them fail. Bump to 2.338.0, the current release. dist/index.js is rebuilt with npm ci && npm run package.
buildUserDataScript took an `idx` parameter that no caller passes (the `$idx` in the script is the bash loop variable), and RunInstances params set SubnetId twice with the same value. Neither change alters behaviour.
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
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
src/aws.jsto 2.338.0 (the current actions/runner release, 2026-10-06) and rebuildsdist/index.js.Verification
npm ci && npm run packagereproduces the committeddist/index.jsbyte-for-byte.npm run lintis clean. The second commit fixes the 2 errors that were already onmainand failed the PR lint check: an unusedidxparameter, andSubnetIdset twice with the same value. Neither changes behaviour.