Skip to content

ci: pin pnpm/action-setup to v6.1.0 (latest available) - #461

Merged
kraenhansen merged 2 commits into
mainfrom
claude/cool-galileo-hfmvmo
Sep 12, 2026
Merged

ci: pin pnpm/action-setup to v6.1.0 (latest available)#461
kraenhansen merged 2 commits into
mainfrom
claude/cool-galileo-hfmvmo

Conversation

@kraenhansen

Copy link
Copy Markdown
Collaborator

What

Audited every third-party action used across .github/workflows/check.yml and .github/workflows/release.yml against its latest available release, per the "verify latest or document why not" policy. This PR is the one action out of the set that needed a change: pnpm/action-setup.

Why

pnpm/action-setup is used with the floating @v6 major tag everywhere in this repo. Upstream's v6 tag currently still points at v6.0.10 (Aug 3, 2026) — it hasn't been moved forward to v6.1.0 (Sep 5, 2026, adds pnpm v12 support). So @v6 was silently not resolving to the latest available version.

Fix: pin to the exact v6.1.0 tag everywhere, mirroring how hendrikmuhs/ccache-action is already pinned to an exact patch in this file (with the same rationale style), and documented the reason next to the existing ccache-action note so a future bump doesn't get "helpfully" reverted back to floating @v6. Once upstream moves the v6 tag past v6.1.0, we can float again.

Audit results for every other action in these workflows

Confirmed each is already on the newest available version (their floating major tag currently resolves to the same commit as the newest specific-version tag):

Action Pinned as Latest available Status
actions/checkout @v7 v7.0.1 ✅ up to date
actions/setup-node @v7 v7.0.0 ✅ up to date
actions/setup-java @v6 v6.0.1 ✅ up to date
actions/upload-artifact @v7 v7.0.1 ✅ up to date
android-actions/setup-android @v4 v4.0.1 ✅ up to date
reactivecircus/android-emulator-runner @v2 v2.38.0 ✅ up to date
aminya/setup-cpp @v1 v1.10.1 ✅ up to date
changesets/action/* @v2 v2.1.2 ✅ up to date (floating v2 branch, not a tag, but it's kept current)
hendrikmuhs/ccache-action @v1.2.24 (exact) v1.2.24 ✅ already the latest, and already has a documented reason for the exact pin. Verified the documented gate ("float again once upstream moves v1/v1.2 to ≥ v1.2.22") still holds — those floating tags are still stuck at v1.2.20.
pnpm/action-setup @v6@v6.1.0 v6.1.0 ❌ was one release behind — fixed in this PR

No other action needed a version bump or a new documented-reason comment.

🤖 Generated with Claude Code

https://claude.ai/code/session_017iWrfmJFUyb3g3SyqgAGb8


Generated by Claude Code

The floating v6 major tag hasn't been moved past v6.0.10, one release
behind v6.1.0 (adds pnpm v12 support), so plain @v6 usage was not
actually running the latest available version. Pin to the exact tag,
matching how hendrikmuhs/ccache-action is already handled, and note
why in the same comment block.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017iWrfmJFUyb3g3SyqgAGb8
@kraenhansen kraenhansen added Apple 🍎 Anything related to the Apple platform (iOS, macOS, Cocoapods, Xcode, XCFrameworks, etc.) Android 🤖 Anything related to the Android platform (Gradle, NDK, Android SDK) Host 🏡 Our `react-native-node-api-modules` package Ferric 🦀 MacOS 💻 Anything related to the Apple MacOS platform or React Native MacOS support weak-node-api labels Sep 12, 2026 — with Claude
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017iWrfmJFUyb3g3SyqgAGb8
@kraenhansen
kraenhansen merged commit 8a732e4 into main Sep 12, 2026
11 checks passed
@kraenhansen
kraenhansen deleted the claude/cool-galileo-hfmvmo branch September 12, 2026 07:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Android 🤖 Anything related to the Android platform (Gradle, NDK, Android SDK) Apple 🍎 Anything related to the Apple platform (iOS, macOS, Cocoapods, Xcode, XCFrameworks, etc.) Ferric 🦀 Host 🏡 Our `react-native-node-api-modules` package MacOS 💻 Anything related to the Apple MacOS platform or React Native MacOS support weak-node-api

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants