chore: bump version to 0.15.0

[MantisClone]

Problem

Need to create a new release for production deployment.

Proposed Solution

Bump minor version from 0.14.0 to 0.15.0 to reflect new features since last release:

• feat: request faucet tokens from app
• fix: move platform fee fields to body level in batchPay endpoint
• feat: add payout confirmation dialogue component that showcases fees
• feat: add payout confirmation component to direct payout
• feat: add payout confirmation component to batch payouts
• feat: add fallback display if no amountInUSD and add protocol fee
• chore: update CTA from book a demo to get in touch

Summary by CodeRabbit

• Chores
  • Version bump to 0.15.0.

---

Note: This release contains no user-facing changes or functional updates.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

Version bump from 0.14.0 to 0.15.0 in package.json. No functional changes, script modifications, or control flow alterations.

Changes

Cohort / File(s)	Summary
Version Update package.json	Version number incremented from 0.14.0 to 0.15.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~1 minute

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The pull request title directly and accurately reflects the main change: updating the package version from 0.14.0 to 0.15.0, which is the sole functional change in the changeset.
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.}

---

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9c273e and bc637ba.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (1)

• package.json

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

**/*: - Only comment on issues that would block merging — ignore minor or stylistic concerns.

• Restrict feedback to errors, security risks, or functionality-breaking problems.
• Do not post comments on code style, formatting, or non-critical improvements.
• Keep reviews short: flag only issues that make the PR unsafe to merge.
• Limit review comments to 3–5 items maximum, unless additional blockers exist.
• Group similar issues into a single comment instead of posting multiple notes.
• Skip repetition — if a pattern repeats, mention it once at a summary level only.
• Do not add general suggestions; focus strictly on merge-blocking concerns.
• If there are no critical problems, respond with minimal approval (e.g., 'Looks good'). Do not add additional review.
• Avoid line-by-line commentary unless it highlights a critical bug or security hole.
• Highlight only issues that could cause runtime errors, data loss, or severe maintainability issues.
• Ignore minor optimization opportunities — focus solely on correctness and safety.
• Provide a top-level summary of critical blockers rather than detailed per-line notes.
• Comment only when the issue must be resolved before merge — otherwise, remain silent.
• When in doubt, err on the side of fewer comments — brevity and blocking issues only.
• Avoid posting any refactoring issues

Files:

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: Build
• GitHub Check: Lint

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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

[greptile-apps]

Greptile Summary

This PR bumps the package version from 0.14.0 to 0.15.0 in preparation for production deployment. The version change is properly synchronized across both package.json and package-lock.json.

• Version incremented correctly following semantic versioning (minor bump for new features)
• All features listed in PR description are verified in git history since 0.14.0
• No dependency changes or other modifications included
• Clean, single-purpose version bump commit

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• Simple version bump with consistent changes across both package files, no code modifications, and verified feature list alignment with git history
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Version bumped from 0.14.0 to 0.15.0 to reflect new features
package-lock.json	Lock file updated to match package.json version 0.15.0

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PJ as package.json
    participant PL as package-lock.json
    participant Repo as Repository
    
    Dev->>PJ: Update version 0.14.0 → 0.15.0
    Dev->>PL: Update version 0.14.0 → 0.15.0
    Dev->>Repo: Commit version bump
    Repo->>Repo: Ready for production deployment

Loading