chore: bump public package versions for next release

[kaladinlight]

Description

Bumps the public @shapeshiftoss/* packages that have unreleased, shippable source changes since their last published npm version, so the publish-packages workflow ships them on the next release (it publishes any package whose package.json version isn't yet on npm, on push to main).

Bump levels reflect the actual change surface, not the conventional-commit tag:

Package	develop	npm	→ new	level	why
swapper	17.7.3	17.7.3	17.8.0	minor	new swappers/exports (BOB Gateway, chainflip Tron, affiliate split)
chain-adapters	11.3.9	11.3.9	11.4.0	minor	new exported Jito MEV module + Abstract chain adapter
utils	1.0.5	1.0.6	1.1.0	minor	new exported asset/chain constants; leapfrogs npm
types	8.6.7	8.6.7	8.6.8	patch	small additive enum/type members
caip	8.16.7	8.16.8	8.16.9	patch	asset-data regen (data only); leapfrogs npm
contracts	1.0.6	1.0.6	1.0.7	patch	internal FOXy ABI removal
unchained-client	10.14.10	10.14.10	10.14.11	patch	fixes only

Not bumped:

• errors — its only change since publish is a test file (not in the published bundle), so nothing shippable changed.
• hdwallet-* and swap-widget — out of scope.

Notes

• Version-only change; workspace:^ deps are link:-based so pnpm-lock.yaml is unaffected (no lockfile diff).
• caip/utils leapfrog the versions already on npm (8.16.8 / 1.0.6) that develop had fallen behind.
• Reflects only merged develop — in-flight swapper refactors on other branches will get their own bump when they land.

Testing

No code change; publish is gated by the existing publish-packages.yml workflow on merge to main.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated several package versions across the codebase to the latest releases.
  • Included minor and patch version bumps for core libraries and client packages.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 219fafcf-dbd4-4549-8beb-c0fb6f4311d1

📥 Commits

Reviewing files that changed from the base of the PR and between f5b0f1c and 6ca5bbd.

📒 Files selected for processing (7)

• packages/caip/package.json
• packages/chain-adapters/package.json
• packages/contracts/package.json
• packages/swapper/package.json
• packages/types/package.json
• packages/unchained-client/package.json
• packages/utils/package.json

✅ Files skipped from review due to trivial changes (6)

• packages/swapper/package.json
• packages/contracts/package.json
• packages/types/package.json
• packages/unchained-client/package.json
• packages/chain-adapters/package.json
• packages/utils/package.json

---

📝 Walkthrough

Walkthrough

This PR updates the version field in seven package.json manifests across the packages workspace (caip, chain-adapters, contracts, swapper, types, unchained-client, utils). No other fields, dependencies, or scripts were changed.

Changes

Package version bumps

Layer / File(s)	Summary
Bump package versions across workspace packages/caip/package.json, packages/chain-adapters/package.json, packages/contracts/package.json, packages/swapper/package.json, packages/types/package.json, packages/unchained-client/package.json, packages/utils/package.json	Version field incremented in each manifest (e.g., caip 8.16.7→8.16.9, chain-adapters 11.3.9→11.4.0, contracts 1.0.6→1.0.7, swapper 17.7.3→17.8.0, types 8.6.7→8.6.8, unchained-client 10.14.10→10.14.11, utils 1.0.5→1.1.0); no other fields changed.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• shapeshift/web#12371: Both PRs edit packages/contracts/package.json, bumping its version field.

Poem

Seven manifests, numbers climb,
A rabbit hops through version time. 🐇
No new features, just a bump,
Patch by patch, and minor jump.
Onward to the next release!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the PR as a version-only bump of public packages for the next release.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/bump-package-versions

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}