Skip to content

chore(deps): bump @ar.io/sdk to 4.0.0-solana.26 (exact, parity)#763

Merged
vilenarios merged 1 commit into
developfrom
chore/bump-sdk-develop
Jun 4, 2026
Merged

chore(deps): bump @ar.io/sdk to 4.0.0-solana.26 (exact, parity)#763
vilenarios merged 1 commit into
developfrom
chore/bump-sdk-develop

Conversation

@vilenarios
Copy link
Copy Markdown
Contributor

Parity/currency bump alongside ar-io-observer#93 (the observer's actual fix).

Context

The observer was blind on Solana staging because @ar.io/sdk@solana.24 bundled the pre-ADR-024 devnet-shrunk contracts client, whose Epoch decoder used failure_counts: [u16; 30] instead of the deployed [u16; 3000] → every following field shifted → prescribed_observers/names decoded as zeros.

ar-io-node is NOT affected by that bug — it uses @ar.io/sdk only for ArNS resolution (arns-names-cache, composite/on-demand-arns-resolver); it never decodes Epoch/prescribed names.

Why bump anyway

  • Aligns onto the same full-size client (@ar.io/solana-contracts@0.5.0-staging.15) the rest of the stack now uses.
  • Replaces the loose caret (^4.0.0-solana.22) with an exact pin — caret drift is exactly what stranded the observer on a stale build.
  • Picks up SDK fixes since .22.

Notes / caveats

  • .22 → .26 touches ArNS-resolution behavior — please let CI run the resolver suite before merge.
  • yarn.lock refreshed with classic yarn 1.22.22 (stays lockfile v1, not berry).
  • Local install hit an unrelated better-sqlite3 node-gyp error under node 24 (native build/env), not a lockfile issue — resolution succeeded and @ar.io/sdk@4.0.0-solana.26 is pinned. CI/Docker builds it in a proper toolchain.

🤖 Generated with Claude Code

Parity/currency bump alongside ar-io-observer (full-size Epoch decoder fix).
The node uses @ar.io/sdk only for ArNS resolution (arns-names-cache,
*-arns-resolver) — it does NOT decode the Epoch account, so it is NOT affected
by the shrunk-Epoch-decoder bug that blinded the observer (solana.24's
devnet-shrunk failure_counts=[u16;30]). Still worth aligning onto the same
full-size client (@ar.io/solana-contracts@0.5.0-staging.15) the rest of the
stack uses, and swapping the loose caret for an exact pin (caret drift is what
stranded the observer on a stale build).

yarn.lock refreshed with classic yarn 1.22.22 (stays lockfile v1, not berry).

NOTE: .22→.26 jump touches ArNS-resolution behavior — let CI run the resolver
suite before merge. (Local install hit an unrelated better-sqlite3 node-gyp
error under node 24; lockfile resolution is unaffected.)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 3, 2026

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c46921c9-c637-40d1-aaeb-5fbf2cf47d24

📥 Commits

Reviewing files that changed from the base of the PR and between 8203036 and 162c48f.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (1)
  • package.json

📝 Walkthrough

Walkthrough

Updates the @ar.io/sdk dependency version from ^4.0.0-solana.22 to 4.0.0-solana.26 in package.json, removing the caret constraint and pinning to a fixed version.

Changes

Dependency Updates

Layer / File(s) Summary
Update @ar.io/sdk dependency version
package.json
The @ar.io/sdk dependency is updated from ^4.0.0-solana.22 to 4.0.0-solana.26, pinning to an exact version instead of allowing compatible patch releases.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • djwhitt
  • karlprieb
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: bumping @ar.io/sdk dependency version and changing from a caret to an exact pin.
Description check ✅ Passed The description is directly related to the changeset, providing context about why the dependency bump was necessary and its implications for ArNS resolution.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/bump-sdk-develop

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@codecov
Copy link
Copy Markdown

codecov Bot commented Jun 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 79.43%. Comparing base (8203036) to head (162c48f).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #763      +/-   ##
===========================================
+ Coverage    79.41%   79.43%   +0.01%     
===========================================
  Files          125      125              
  Lines        46457    46457              
  Branches      3560     3560              
===========================================
+ Hits         36896    36903       +7     
+ Misses        9514     9507       -7     
  Partials        47       47              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@vilenarios vilenarios merged commit 765ad57 into develop Jun 4, 2026
6 of 7 checks passed
@vilenarios vilenarios deleted the chore/bump-sdk-develop branch June 4, 2026 00:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant