Increment build version to 1.0.9

[AnthonyRonning]

Updated version numbers across all configuration files:

• frontend/package.json: 1.0.8 → 1.0.9
• frontend/src-tauri/tauri.conf.json: 1.0.8 → 1.0.9
• frontend/src-tauri/Cargo.toml: 1.0.8 → 1.0.9
• frontend/src-tauri/gen/apple/maple_iOS/Info.plist: 1.0.5 → 1.0.9
• frontend/src-tauri/gen/apple/project.yml: 1.0.2 → 1.0.9

Fixes #83

Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated application version number to 1.0.9 across relevant files.

[coderabbitai]

Walkthrough

The version numbers for the frontend application have been incremented from 1.0.8 to 1.0.9 in three files: frontend/package.json, frontend/src-tauri/Cargo.toml, and frontend/src-tauri/tauri.conf.json. No other changes were made.

Changes

Files	Change Summary
frontend/package.json	Incremented version from 1.0.8 to 1.0.9
frontend/src-tauri/Cargo.toml, frontend/src-tauri/tauri.conf.json	Incremented version from 1.0.8 to 1.0.9

Assessment against linked issues

Objective (Issue #)	Addressed	Explanation
Increment the build version (#83)	✅

Possibly related PRs

• Bump os to 0.3.5 #9: Updates a dependency version in frontend/package.json, related by version management.
• Bumpt to 1.0.6 #72: Performs a similar version bump in the same set of files, indicating a directly related change.

Poem

A hop, a skip, a version bump,
From eight to nine, we take the jump!
With numbers new, our code will shine,
The Maple build is now one point oh point nine.
🐇✨

---

📜 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 72b2d32 and c6fc18b.

⛔ Files ignored due to path filters (2)

• 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)

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: build-macos (universal-apple-darwin)
• GitHub Check: build-linux
• GitHub Check: build-ios
• GitHub Check: Cloudflare Pages

🔇 Additional comments (3)

frontend/src-tauri/tauri.conf.json (1)

4-4:

Details

✅ Verification successful

Approve version bump
The version field has been correctly updated from 1.0.8 to 1.0.9, matching the intended release.

Ensure no stale version references
To verify that all previous version strings (1.0.8, 1.0.5, 1.0.2) have been replaced across the repo, run this script and confirm it returns no hits:

---

🏁 Script executed:

#!/bin/bash
# Search for any remaining old version references
rg -n '1\.0\.(8|5|2)'
# Expected: no output

Length of output: 4540

---

Approve version bump
The version field in frontend/src-tauri/tauri.conf.json has been correctly updated to 1.0.9.

Ignore lock files when searching for stale app‐version strings
Lock files like bun.lock and Cargo.lock will naturally contain dependency versions and can be skipped. To confirm there are no lingering references to the old app version (1.0.8), run one of these:

• Exclude lock files by globbing:

rg -n --glob='!{bun.lock,Cargo.lock}' '"1\.0\.8"' .

• Or target only your Tauri config:

rg -n 'version"\s*:\s*"1\.0\.8"' frontend/src-tauri/tauri.conf.json

Expected result in both cases: no matches. No further changes are required.

frontend/package.json (1)

4-4: Approve version bump
The version in package.json has been correctly incremented to 1.0.9, aligning with the frontend release.

frontend/src-tauri/Cargo.toml (1)

3-3: Approve version bump
The Cargo manifest’s version is now 1.0.9, consistent with the other frontend artifacts.

---

🪧 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.
  • Explain this complex logic.
  • 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. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• 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 src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

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

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai 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

Documentation and Community

• 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]

PR Summary

Version numbers have been synchronized across all configuration files to 1.0.9, addressing inconsistencies in iOS configuration files that were previously at 1.0.2 and 1.0.5.

• Updated iOS configuration files (frontend/src-tauri/gen/apple/project.yml and frontend/src-tauri/gen/apple/maple_iOS/Info.plist) from outdated versions to 1.0.9
• Synchronized version numbers in core configuration files (frontend/package.json, frontend/src-tauri/Cargo.toml, frontend/src-tauri/tauri.conf.json) from 1.0.8 to 1.0.9

_{5 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}