Bump to 1.2.1

[AnthonyRonning]

Summary by CodeRabbit

• Chores
  • Updated application version to 1.2.1 across the frontend and desktop build configuration.
  • No functional changes; behavior remains the same.
  • Users may see the updated version in the app’s About screen and installers.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Version metadata updated from 1.2.0 to 1.2.1 across frontend package.json, Tauri Cargo.toml, and tauri.conf.json. No functional or configuration changes beyond version fields.

Changes

Cohort / File(s)	Summary of Changes
Version bump metadata frontend/package.json, frontend/src-tauri/Cargo.toml, frontend/src-tauri/tauri.conf.json	Incremented version from 1.2.0 to 1.2.1 in package/app metadata fields only.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• chore: bump version to 1.1.4 #136 — Performs the same version field bumps in the same three frontend files.
• Bumpt to 1.0.6 #72 — Updates identical version keys across package.json, Cargo.toml, and tauri.conf.json.
• Bump to 1.1.3 #113 — Direct version increments in the same frontend metadata files.

Poem

Hop, hop—tick the version line,
1.2.1 now looks quite fine.
I nibble carrots, sign the tag,
release notes bundled in my bag.
Thump of paws—ship it, run!
Another patch, another bun.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 4cc85df and 5fe1eb7.

⛔ Files ignored due to path filters (3)

• frontend/src-tauri/Cargo.lock is excluded by !**/*.lock
• frontend/src-tauri/gen/apple/maple_iOS/Info.plist is excluded by !**/gen/**
• frontend/src-tauri/gen/apple/project.yml is excluded by !**/gen/**

📒 Files selected for processing (3)

• frontend/package.json (1 hunks)
• frontend/src-tauri/Cargo.toml (1 hunks)
• frontend/src-tauri/tauri.conf.json (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update-api-key-documentation-links

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[greptile-apps]

Greptile Summary

This PR performs a coordinated version bump from 1.2.0 to 1.2.1 across all platform configuration files in the Maple application. The changes update version numbers in five key files: the frontend package.json, Rust Cargo.toml, Tauri configuration tauri.conf.json, iOS Info.plist, and Xcode project.yml. This is a standard patch release increment following semantic versioning conventions.

The version synchronization is critical for Tauri applications since they involve multiple technology stacks - the frontend JavaScript/TypeScript components, Rust backend, desktop application configuration, and mobile iOS builds all need consistent versioning. The Tauri updater system (configured in tauri.conf.json) relies on this version field to determine when updates are available to users. Similarly, iOS App Store submissions require proper version metadata in the Info.plist and project configuration files.

This type of coordinated version bump is typical in the Maple project's release workflow, where a single command likely updates all relevant configuration files simultaneously to maintain consistency across the entire application stack. The patch version increment suggests this release contains bug fixes or minor improvements rather than new features or breaking changes.

Confidence score: 5/5

• This PR is extremely safe to merge with no risk of production issues
• Score reflects simple, standard version number updates across configuration files with no logic changes
• No files require special attention - all changes are straightforward version increments

_{5 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}