Repository navigation
Conversation
This was referenced Oct 22, 2026
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.
CI still ran actions/checkout@v4 and actions/setup-node@v4, which run on the deprecated node20 runtime. The dependabot PRs for these bumps (#4, #5) are based on main history that was later rewritten, so each carries 15 stale commits and conflicts. #2 (setup-bun 1 to 2) is obsolete because main already uses setup-bun@v2.
This bumps every checkout use to v7.0.1 and every setup-node use to v7.1.0 (release.yml was already on v6), and pins checkout, setup-node and oven-sh/setup-bun (v2.2.0) by full commit SHA with a version comment, so dependabot can keep them current.
I read the v5, v6 and v7 release notes of both actions. Checkout v6 moves persisted credentials to a separate file and v7 blocks fork-PR checkout under pull_request_target and workflow_run; we do no raw git push after checkout and use neither trigger. Setup-node v5/v6 auto-caching only applies to npm via packageManager, which package.json does not set, and the v7 NODE_AUTH_TOKEN change only matters with registry-url, which we do not use.
bun run verifypasses locally (1322 unit, 529 integration tests).Supersedes #2, #4, #5.
Not verified: release workflow (only a real release runs release.yml), e2e tiers.