Bump version from 0.0.10 to 0.0.11

[MarkSackerberg]

No description provided.

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Version bumped to 0.0.11.

Walkthrough

Package version incremented from 0.0.10 to 0.0.11 in package.json.

Changes

Cohort / File(s)	Summary
Version Bump package.json	Version field updated from "0.0.10" to "0.0.11".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• bump version #28: Makes the exact same type of change—incrementing the package.json "version" field.
• Bump version to 0.0.10 #61: Modifies the same package.json "version" field with sequential version bumps.

Suggested reviewers

• danenbm
• blockiosaurus

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	No description was provided by the author, making it impossible to assess relevance to the changeset.	Add a brief description explaining the purpose of the version bump (e.g., release notes, bug fixes, or new features included).

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: updating the package version from 0.0.10 to 0.0.11 in package.json.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch chore/version

---

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 and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (2)

package.json (2)

50-50: 🧹 Nitpick | 🔵 Trivial

@solana/web3.js 1.x is now in maintenance mode — plan migration to @solana/kit.

The 1.x line of @solana/web3.js is now the maintenance branch; the successor library is @solana/kit. The current ^1.98.2 caret range safely prevents accidentally pulling in the breaking v2 API, but a migration to @solana/kit should be tracked.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 50, The dependency listing uses "@solana/web3.js":
"^1.98.2" which is now maintenance-only; replace tracking of this package with
the successor "@solana/kit" and plan a migration: update package.json to add
"@solana/kit" (and remove or pin "@solana/web3.js" only if you need temporary
compatibility), search for imports/usages of "import ... from '@solana/web3.js'"
and migrate those call sites to the new "@solana/kit" API (or add compatibility
wrappers) ensuring tests build; also add a short TODO/issue in the repo
referencing the migration so it isn't forgotten.

---

27-27: ⚠️ Potential issue | 🟡 Minor

@inquirer/testing belongs in devDependencies, not dependencies.

This is a test utility and should not be a runtime dependency. It unnecessarily inflates the production install footprint.

📦 Proposed fix

   "dependencies": {
     "@ardrive/turbo-sdk": "^1.25.0",
     "@inquirer/prompts": "^7.5.3",
-    "@inquirer/testing": "^2.1.47",
     ...
   },
   "devDependencies": {
+    "@inquirer/testing": "^2.1.47",
     "@metaplex-foundation/amman": "^0.12.1",

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 27, Move the test utility "@inquirer/testing" out of
the package.json "dependencies" section into "devDependencies": remove the
"@inquirer/testing" entry from dependencies and add the same entry (same version
^2.1.47) under devDependencies, then update the lockfile (npm/yarn/pnpm) by
reinstalling so production installs no longer include this package.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@package.json`:
- Line 50: The dependency listing uses "@solana/web3.js": "^1.98.2" which is now
maintenance-only; replace tracking of this package with the successor
"@solana/kit" and plan a migration: update package.json to add "@solana/kit"
(and remove or pin "@solana/web3.js" only if you need temporary compatibility),
search for imports/usages of "import ... from '@solana/web3.js'" and migrate
those call sites to the new "@solana/kit" API (or add compatibility wrappers)
ensuring tests build; also add a short TODO/issue in the repo referencing the
migration so it isn't forgotten.
- Line 27: Move the test utility "@inquirer/testing" out of the package.json
"dependencies" section into "devDependencies": remove the "@inquirer/testing"
entry from dependencies and add the same entry (same version ^2.1.47) under
devDependencies, then update the lockfile (npm/yarn/pnpm) by reinstalling so
production installs no longer include this package.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a83d7e9 and 550ec68.

📒 Files selected for processing (1)

• package.json