[piotr-iohk]

Description

Record the shipped Bitkit 3.1.1 build 204 on master. Copy the published changelog and remove the fragments already included in it so the next release does not repeat those entries. Published 3.1.1 release · Release PR

Design

N/A — no UI changes.

Preview

N/A

QA Notes

Compared the Xcode version fields and changelog with the published v3.1.1 tag. plutil -lint Bitkit.xcodeproj/project.pbxproj and git diff --check passed. Mainnet QA covers the shipped tag. 3.1.1 QA results

Models used

• Planning/scoping: GPT-6 (reasoning: Not exposed)
• Implementation: GPT-6 (reasoning: Not exposed)
• Review: Not performed

The session exposes the model family. The reasoning setting is unavailable.

[greptile-apps]

Confidence Score: 5/5

[Low impact] This PR appears safe to merge.

Summary

Records the shipped iOS 3.1.1 release on master.

• Bitkit builds now carry the 3.1.1 version and 204 build number.
• The changelog now records 3.1.1 and starts the next release after it.

The recorded versions and changelog match v3.1.1. git diff --check passed. No actionable issues were found.

_{Reviews (1) · Last reviewed commit: "chore: record iOS 3.1.1 release" · Reviewed by Greptile}

[talosmachina]

No findings. Records the shipped 3.1.1 (build 204) on master: MARKETING_VERSION and CURRENT_PROJECT_VERSION in all six app, widget and notification build configurations, the 3.1.1 changelog section and compare links, and removal of the three fragments it consumed. Reviewed e15aeef, full tier, static (iOS does not build on Linux; reasoned from the diff, the v3.1.1 tag and CI).

What I checked, and 3 candidates I ruled out

Against the tag: CHANGELOG.md on the PR head is byte-identical to CHANGELOG.md at v3.1.1; the version settings in project.pbxproj match the tag exactly (6 configurations at 3.1.1 / 204, the 4 test-target configurations still at 1.0 / 1, as at the tag).
Base: the merge base is the current master tip (21e87d6), so nothing on master is overwritten.

Ruled out

• A configuration left at 3.1.0 / 203: none remain; the widget and notification extensions move with the app, so the embedded-bundle version check holds.
• A consumed fragment left behind, or an unreleased one deleted: the three entries with fragments on master (#1235, #1237, #1290) are the three deleted; #1252 and #1292 never had one on master. A keyword pass over the 24 remaining fragments matched none of the 3.1.1 entries.
• Compare links: [Unreleased] now starts at v3.1.1 and [3.1.1] spans v3.1.0...v3.1.1.

CI: Greptile, SwiftFormat and validate passed; Run Tests, Run Integration Tests and build-local were pending when this was posted.

Merge confidence: 4/5, the change is version fields and changelog only, but CI was still running at review time.

[ovi-reviewer]

Verdict: ✅ Ready to release — the recorded metadata matches the already published 3.1.1 release.

Findings: None.

QA for e15aeef:

Check: Shipping versions match the published release ✅ Parsed project settings match 3.1.1, build 204, in every app and extension configuration.

Compared all six shipping configurations with the published v3.1.1 tag. The only project-setting changes against the base are the marketing and build versions; test-target settings stay unchanged.

Check: Release history consumes only published fragments ✅ Git comparisons confirm the changelog matches the tag and all deleted fragments are included.

CHANGELOG.md is byte-identical to the tag. Each deleted fragment appears verbatim in the 3.1.1 section, every remaining fragment is unchanged, and the next-release comparison starts at v3.1.1.

Check: Project and patch remain valid ✅ Project lint and whitespace checks pass.

plutil -lint Bitkit.xcodeproj/project.pbxproj and git diff --check both passed at e15aeef.

No application build or device run: this PR lists static release checks and changes only version metadata and release history. It adds no runtime behavior or device cases. These results do not claim fresh mainnet QA of the shipped release.

The existing static review also reports no findings at this head; the checks above were independently repeated.

Twin: bitkit-android#1904 chore: record Android 3.1.1 release matches the release-recording scope, with platform-specific build numbers and changelog entries.

Reviewed the full five-file diff. All changed content was checked statically; none was driven on a device.

---

Reviewed by gpt-6.1-sol-high

[ben-kaufman]

No material findings in the version and changelog changes recording the shipped 3.1.1 build 204. The recorded versions and changelog match the published release. I have not run fresh device QA or verified binary packaging.

Reviewer model: gpt-6.1-sol
Reasoning effort: xhigh