chore(deps): Bump actions/setup-node from 4 to 6 - #2
Merged
graveyieldprotocol merged 1 commit intoMay 10, 2026
Merged
Conversation
Bumps [actions/setup-node](https://github.com/actions/setup-node) from 4 to 6. - [Release notes](https://github.com/actions/setup-node/releases) - [Commits](actions/setup-node@v4...v6) --- updated-dependencies: - dependency-name: actions/setup-node dependency-version: '6' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
graveyieldprotocol
added a commit
that referenced
this pull request
May 19, 2026
Same ci.yml change as PR #19's fixup #2: Solana 3.0.10's bundled platform-tools v1.51 ships cargo 1.84 which can't parse `edition2024` manifests pulled transitively by Anchor 0.32.1's SPL deps. Replace the cached platform-tools directory with v1.54 (cargo 1.89) before anchor build invokes cargo-build-sbf. m6's Rust code itself is BPF-clean — `cargo-build-sbf` succeeds locally once platform-tools v1.54 is active. The only change here is the CI workflow step. If PR #19 lands first with the same ci.yml change, this PR's rebase resolves trivially (identical content). If PR #20 lands first, PR #19 rebases against this. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
graveyieldprotocol
added a commit
that referenced
this pull request
May 19, 2026
Locally reproduced: `anchor build` passes the BPF compile stage (cargo-build-sbf finishes clean with platform-tools v1.54 in place from fixup #2) but fails the IDL-generation stage: info: syncing channel updates for nightly-x86_64-unknown-linux-gnu error: could not download file from 'https://static.rust-lang.org/...' Error: Building IDL failed. Anchor 0.32.1's `anchor idl build` still invokes rustup to install a nightly toolchain, which the workflow's `dtolnay/rust-toolchain@stable` step doesn't pre-install. The CI runner can reach static.rust-lang.org in principle, but rustup's auto-install path needs an explicit toolchain declared. Fix: pass `--no-idl` to skip IDL generation. The on-chain program builds and verifies correctly without IDL; IDL is only required for TypeScript client type generation, which is a separate workstream (can land later as a CI step that installs nightly before invoking `anchor idl build`). Verified locally with anchor-cli 0.32.1 + platform-tools v1.54 + Solana 3.0.10: anchor build --no-idl → Finished `release` profile in 5.67s (clean) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
graveyieldprotocol
added a commit
that referenced
this pull request
May 19, 2026
Locally reproduced: `anchor build` passes the BPF compile stage (cargo-build-sbf finishes clean with platform-tools v1.54 in place from fixup #2) but fails the IDL-generation stage: info: syncing channel updates for nightly-x86_64-unknown-linux-gnu error: could not download file from 'https://static.rust-lang.org/...' Error: Building IDL failed. Anchor 0.32.1's `anchor idl build` still invokes rustup to install a nightly toolchain, which the workflow's `dtolnay/rust-toolchain@stable` step doesn't pre-install. The CI runner can reach static.rust-lang.org in principle, but rustup's auto-install path needs an explicit toolchain declared. Fix: pass `--no-idl` to skip IDL generation. The on-chain program builds and verifies correctly without IDL; IDL is only required for TypeScript client type generation, which is a separate workstream (can land later as a CI step that installs nightly before invoking `anchor idl build`). Verified locally with anchor-cli 0.32.1 + platform-tools v1.54 + Solana 3.0.10: anchor build --no-idl → Finished `release` profile in 5.67s (clean) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
graveyieldprotocol
added a commit
that referenced
this pull request
May 19, 2026
Step-level CI timing on fixup #3 reveals the actual failure: Step 7 'Install Anchor CLI' completed in 0s conclusion=success Step 8 'Pin platform-tools v1.54' completed in 48s conclusion=success Step 9 'Anchor build' completed in 1s conclusion=failure `cargo binstall --no-confirm --version 0.32.1 anchor-cli` silently no-ops on anchor-cli 0.32.x — it exits 0 without installing `anchor` on PATH, then `anchor build` exits immediately (1s) because the binary doesn't exist. This is the same silent-no-op pattern I have in failure-pattern memory; I had closed PR #18 thinking cargo-binstall was working (based on PR #17's intermittent success), but it's actually flaky/broken for 0.32.x consistently. Fix: replace cargo binstall with `cargo install --locked --version 0.32.1 anchor-cli` + an `anchor --version` assertion. Source compile takes ~5-7 min on a cold cache but is cached by Swatinem/rust-cache@v2, so steady-state CI time is unchanged. The version assertion fails the install step itself on any future regression instead of deferring to the build step where the symptom is opaque (0s install + 1s build failure is harder to diagnose than a clean install-step failure). Combined with fixup #2 (platform-tools v1.54) and fixup #3 (--no-idl to skip nightly-Rust IDL generation), this should clear anchor build. Locally verified all three together produce a clean `anchor build --no-idl` in 5.67s on m5 and 5.02s on m6. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
graveyieldprotocol
added a commit
that referenced
this pull request
May 19, 2026
Step-level CI timing on fixup #3 reveals the actual failure: Step 7 'Install Anchor CLI' completed in 0s conclusion=success Step 8 'Pin platform-tools v1.54' completed in 48s conclusion=success Step 9 'Anchor build' completed in 1s conclusion=failure `cargo binstall --no-confirm --version 0.32.1 anchor-cli` silently no-ops on anchor-cli 0.32.x — it exits 0 without installing `anchor` on PATH, then `anchor build` exits immediately (1s) because the binary doesn't exist. This is the same silent-no-op pattern I have in failure-pattern memory; I had closed PR #18 thinking cargo-binstall was working (based on PR #17's intermittent success), but it's actually flaky/broken for 0.32.x consistently. Fix: replace cargo binstall with `cargo install --locked --version 0.32.1 anchor-cli` + an `anchor --version` assertion. Source compile takes ~5-7 min on a cold cache but is cached by Swatinem/rust-cache@v2, so steady-state CI time is unchanged. The version assertion fails the install step itself on any future regression instead of deferring to the build step where the symptom is opaque (0s install + 1s build failure is harder to diagnose than a clean install-step failure). Combined with fixup #2 (platform-tools v1.54) and fixup #3 (--no-idl to skip nightly-Rust IDL generation), this should clear anchor build. Locally verified all three together produce a clean `anchor build --no-idl` in 5.67s on m5 and 5.02s on m6. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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
1 participant
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps actions/setup-node from 4 to 6.
Release notes
Sourced from actions/setup-node's releases.
... (truncated)
Commits
48b55a0Update Node.js versions in versions.yml and bump package to v6.4.0 (#1533)ab72c7eUpgrade@actionsdependencies (#1525)53b8394Bump minimatch from 3.1.2 to 3.1.5 (#1498)54045abScope test lockfiles by package manager and update cache tests (#1495)c882bffReplace uuid with crypto.randomUUID() (#1378)774c1d6feat(node-version-file): support parsingdevEnginesfield (#1283)efcb663fix: remove hardcoded bearer (#1467)d02c89dFix npm audit issues (#1491)6044e13Docs: bump actions/checkout from v5 to v6 (#1468)8e49463Fix README typo (#1226)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)