fix/update-intent-sdk-version

[RanaBug]

Description

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Summary by CodeRabbit

• Chores
  • Updated internal dependency to @etherspot/intent-sdk 1.0.0-alpha.10.
  • Aligns with the latest SDK release to maintain compatibility with upstream changes.
  • No user-facing functionality or behavior changes are expected from this update.
  • Routine maintenance to keep dependencies current and reduce potential integration issues.
  • Minimal risk; no user action required.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated dependency version in package.json: @etherspot/intent-sdk from 1.0.0-alpha.9 to 1.0.0-alpha.10. No other files or exports changed.

Changes

Cohort / File(s)	Summary
Dependency version bump package.json	Bumped @etherspot/intent-sdk from 1.0.0-alpha.9 to 1.0.0-alpha.10; no other modifications shown.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

• IAmKio
• ch4r10t33r

Poem

I nudge a number, hop—so slight,
From alpha.9 to .10 in light.
Dependencies snug, my whiskers twitch,
No code to churn, no logic glitch.
A carrot toast to tidy flow—
Patch by patch, we onward go. 🥕🐇

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/update-intent-sdk-version

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c0f3a76 and 965575e.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (1)

• package.json (1 hunks)

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

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.}