release: 0.1.1 build 2, because build 1 expired in TestFlight before anyone installed it

[GeiserX]

Build 0.1.0 (1) reached App Store Connect this morning, processed as valid, and then showed up as Expired four hours later, before the TestFlight invitation could install anything. An expired build cannot be brought back, and the release workflow refuses a tag that does not match the marketing version, so the next upload needs a new version and a higher build number.

This bumps project.yml to 0.1.1 build 2 and the README status line with it. Nothing else changes. Tag v0.1.1 on the merge commit runs the upload.

Summary by CodeRabbit

• Release Information
  • Updated the app version to 0.1.1 and build number to 2.
  • Updated the README to reflect preparation for TestFlight and the App Store.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: GeiserX/TG-Archive-iOS/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: a9c38568-d67d-40a3-82b2-2fbd4832a627

📥 Commits

Reviewing files that changed from the base of the PR and between 918974a and a41f152.

📒 Files selected for processing (2)

• README.md
• project.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The README now identifies v0.1.1 as being prepared for TestFlight and the App Store. The project marketing version is 0.1.1, and the build number is 2.

Changes

Release Version Update

Layer / File(s)	Summary
Update release version metadata README.md, project.yml	The README status and project settings now identify version 0.1.1. The project build number changes to 2.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to a41f1

The release metadata consistently identifies v0.1.1 and build 2, and the release workflow accepts the matching v0.1.1 tag. No actionable merge-blocking risk remains.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main changes: version 0.1.1 and build 2. It also gives the release reason.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

---

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