chore: bump version to 0.5.2

[MantisClone]

Problem

Need to create a new release for production deployment.

Proposed Solution

Bump version from 0.5.1 to 0.5.2.

Summary by CodeRabbit

• Chores
  • Version bump: Updated package version from 0.5.1 to 0.5.2.

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

[coderabbitai]

Walkthrough

The pull request bumps the package version from 0.5.1 to 0.5.2 in package.json. No functional changes, scripts, dependencies, or configuration modifications are included.

Changes

Cohort / File(s)	Summary
Version Update package.json	Version field updated from "0.5.1" to "0.5.2"

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 title clearly and accurately describes the only change in the pull request: bumping the version number from 0.5.1 to 0.5.2.
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 a61605f and b88ff6e.

📒 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). (1)

• GitHub Check: Build

_{✏️ 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 increments the patch version from 0.5.1 to 0.5.2, preparing the application for a production deployment.

• Single-line version change in package.json following semantic versioning
• No code changes, dependencies, or configuration modifications included

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a simple version number increment in package.json with no code modifications, dependency updates, or configuration changes that could introduce bugs or breaking changes
• No files require special attention

Important Files Changed

Filename	Overview
package.json	Version bumped from 0.5.1 to 0.5.2 for patch release

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant PJ as package.json
    participant Release as Release Process
    
    Dev->>PJ: Update version field
    PJ-->>PJ: Change "0.5.1" to "0.5.2"
    Dev->>Release: Commit version bump
    Release->>Release: Tag as v0.5.2
    Release->>Release: Deploy to production

Loading