chore: bump version to 1.1.0 (build 5)

[eulicesl]

Version bump for the v1.1.0 TestFlight release. Archive exported and IPA ready for upload via Transporter.

Summary by CodeRabbit

• Chores
  • Updated application version to 1.1.0.

[coderabbitai]

Warning

Rate limit exceeded

@eulicesl has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 58 minutes and 14 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 58 minutes and 14 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 957caf5c-1cc4-499c-a1bd-7f6ce220e24e

📥 Commits

Reviewing files that changed from the base of the PR and between f3cf23d and 9cc1d80.

📒 Files selected for processing (1)

• Lumen.xcodeproj/project.pbxproj

📝 Walkthrough

Walkthrough

Very good, Sir. The project configuration has been updated to reflect a minor version increment. The CURRENT_PROJECT_VERSION has been advanced from 4 to 5, whilst the MARKETING_VERSION has been updated from 1.0.0 to 1.1.0 across the primary build configurations and widget-related targets.

Changes

Cohort / File(s)	Summary
Build Configuration Updates Lumen.xcodeproj/project.pbxproj	Version numbers incremented: CURRENT_PROJECT_VERSION (4 → 5) and MARKETING_VERSION (1.0.0 → 1.1.0) across multiple XCBuildConfiguration entries for the app target and widget configurations.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

A version ascends with grace,
From 1.0 to 1.1's embrace,
Build number climbs,
In measured times,
The app assumes its proper place. ✨📱

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is minimal and lacks the required structured sections from the template, including Summary, Change Type, Scope, Security & Privacy Impact, and Human Verification components.	Expand the description to include required template sections: explicitly state the Problem and Why it matters, select appropriate Change Type (Chore/infra) and Scope (Build/signing/release), complete Security & Privacy Impact assessment, and detail verification steps taken.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and concisely describes the main change: a version bump to 1.1.0 with build number 5, which directly corresponds to the modifications in the project file.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/happy-williams-00c2e8

---

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

[gemini-code-assist]

Code Review

This pull request updates the project version to 5 and the marketing version to 1.1.0 across the Xcode project configuration. The review feedback suggests centralizing the MARKETING_VERSION at the project level by removing redundant overrides at the target level, which would improve maintainability and prevent potential synchronization issues.

I am having trouble creating individual review comments. Click here to see my feedback.

Lumen.xcodeproj/project.pbxproj (1014)

The MARKETING_VERSION is already defined at the project level (lines 967 and 1113). Since the value is identical, defining it again at the target level is redundant and can lead to synchronization issues in the future. Consider removing this override to let the target inherit the version from the project, as is already done for CURRENT_PROJECT_VERSION.

References

1. Centralize simple, duplicated logic or configuration values into a dedicated location to ensure consistency and improve maintainability.

Lumen.xcodeproj/project.pbxproj (1161)

The MARKETING_VERSION is already defined at the project level (lines 967 and 1113). Since the value is identical, defining it again at the target level is redundant and can lead to synchronization issues in the future. Consider removing this override to let the target inherit the version from the project, as is already done for CURRENT_PROJECT_VERSION.

References

1. Centralize simple, duplicated logic or configuration values into a dedicated location to ensure consistency and improve maintainability.