[piotr-iohk]

Description

Record the shipped Bitkit 3.1.1 build 197 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 Gradle version fields and changelog with the published v3.1.1 tag. 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 release-recording change appears safe to merge.

Summary

Records the shipped Android 3.1.1 build 197 on master.

• Bitkit’s project records now identify the shipped 3.1.1 release.

No actionable issues found.

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

[talosmachina]

No findings. Records the shipped 3.1.1 (build 197) on master: version fields, the 3.1.1 changelog section and compare links, and removal of the four fragments it consumed. Reviewed 0443ae5, full tier, static (Bitkit Android branches are not built here; 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; versionCode = 197 and versionName = "3.1.1" match the tag's app/build.gradle.kts.
Base: the merge base is the current master tip (db3b1b2), so nothing on master is overwritten.

Ruled out

• A consumed fragment left behind, so 3.1.1 entries repeat in the next release: the four entries with fragments on master (#1798, #1801, #1803, #1870) are the four deleted; #1824 and #1873 never had a fragment on master. A keyword pass over the 26 remaining fragments matched none of the 3.1.1 entries (the two "Lightning node" hits, #1536 and #1756, are different fixes).
• An unreleased fragment deleted by mistake: only the four above are removed.
• Compare links: [Unreleased] now starts at v3.1.1 and [3.1.1] spans v3.1.0...v3.1.1, consistent with the existing entries.

CI: Greptile passed; build-and-test, lint, build-local and compose-ui 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.

[github-actions]

Regtest APK

Built from 0443ae5 (run).

Download bitkit-dev-debug universal APK (expires in 30 days).

[ovi-reviewer]

Verdict: 💬 Comment. The release record matches published v3.1.1; current-head Compose UI CI is failing.

Findings: None.

QA for 0443ae5:

Check: Match the published release ✅ Static comparison confirms version 3.1.1, build 197, and the published changelog.

CHANGELOG.md is byte-identical to the published tag, which points to 0f23fc2. The Gradle version fields also match that tag.

Check: Preserve unreleased changelog entries ✅ Static inspection confirms the four deleted fragments are recorded in 3.1.1 and the remaining entries are preserved.

Each of the four deleted fragments appears verbatim in the published changelog. The 26 remaining fragments describe other changes. The release comparison links are correct, and git diff --check passes for db3b1b2..0443ae5.

Check: Current-head CI ⚠️ Builds, unit tests, lint and local E2E pass, but Compose UI has eight failures.

The Compose UI job reports six window-focus failures and two Compose timeouts. Its failure also fails the aggregate build check; the build-and-test job itself passed. Lint and local E2E also passed. I have not reproduced the Compose failures against the base or established that this PR causes them.

No app build or device cases were run for this review: the QA notes list static checks, and this diff only records release metadata and consumes changelog fragments. The linked release QA spreadsheet required authentication, so I did not use it as evidence. The earlier review at this head agrees with the independently checked release-record comparisons.

Full review covered all six changed files in db3b1b2..0443ae5. No runtime or test sources changed.

Twin: bitkit-ios#1319 chore: record iOS 3.1.1 release matches this release-record scope, using iOS build 204 and its platform-specific changelog entries.

---

Reviewed by gpt-6.1-sol-high

[piotr-iohk]

The Compose UI failure flagged in the review cleared on the unchanged 0443ae5 commit. The retry ran all 257 Compose UI tests and passed the aggregate build check. The first attempt's window-focus errors and Compose timeouts did not reproduce.

[jvsena42]

No findings. Reviewed 0443ae5 against the published v3.1.1 tag.

• The ## [3.1.1] section of CHANGELOG.md is identical to the tag's; versionCode = 197 / versionName = "3.1.1" match the tag's app/build.gradle.kts.
• v3.1.0..v3.1.1 ships #1798, #1801, #1803, #1824, #1865, #1872, #1873. The four fragments deleted (1798, 1801, 1803, 1870) are the only ones on master covering them; #1870's entry ships through its cherry-pick #1872. The 26 remaining fragments are all unreleased.
• Compare links: [Unreleased] starts at v3.1.1, [3.1.1] spans v3.1.0...v3.1.1.
• CI at this head: all 18 checks green (the Compose UI failures noted earlier are gone).

Device gate: no device check needed — version fields and changelog only. perf: not relevant.