Release v1.2.0 and re-pin keep to b06b61f

[kwsantiago]

Summary

Prepares v1.2.0: versionCode 27 to 28, versionName 1.1.9 to 1.2.0, and re-pins keep.version from 88dd3bc to b06b61f.

Why the re-pin matters here

keep.version decides which keep core gets built into the app, and it had fallen four commits behind keep's main. One of those is load-bearing for this release:

keep commit		relevant to Android
95e7626 (#932)	Never let a degraded RNG path succeed quietly	yes, keep-core/src/entropy.rs
e98cea6 (#933)	Mark a FROST nonce used when it is claimed	no, keep-cli only
9cfe24a (#931)	Stop the rate-limit tests racing the derivation	no, keep-core test fix
b06b61f (#934)	Keep the job token out of a PR-controlled tree	no, CI only

#470 landed the Android side of the degraded-RNG work, but the pinned core still predated the core-side fix in keep-core/src/entropy.rs. Releasing on the old pin would have shipped one half of that change without the other. The re-pin is what makes the release coherent, not housekeeping alongside it.

Release contents

Five commits since v1.1.9:

• Never let a degraded RNG path succeed quietly #470 Never let a degraded RNG path succeed quietly
• Never erase the legacy share until a copy is demonstrably stored #469 Never erase the legacy share until a copy is demonstrably stored
• Bind stored values to the key they are stored under #468 Bind stored values to the key they are stored under
• Qualify the request label only when nothing verified it #467 Qualify the request label only when nothing verified it
• Show the request label in the co-sign prompt #466 Show the request label in the co-sign prompt

Minor rather than patch: #468 changes how stored values are bound to their key, and #469 changes share-deletion ordering.

Test plan

• verifyKeepVersion passes against b06b61f
• keep.version is a 40-char lowercase hex SHA that exists on keep's main, matching the format gate in build.gradle.kts
• No-trailing-newline format of keep.version preserved, so the diff is the SHA alone
• Build verification is CI's. build.gradle.kts requires JDK 21 for any assemble/compile/lint task and this machine has only JDK 17, so no local assembleDebug was run. The APK build, lint, locale-drift and hardcoded-string gates all need to pass here before this is merged or tagged.

verifyKeepVersion was run against a throwaway clone via KEEP_REPO rather than the local keep symlink. The task's own failure message suggests reset --hard plus clean -fdx on that path, which resolves to the real keep repository and would delete untracked work there.

Summary by CodeRabbit

• Chores
  • Updated the Android app to version 1.2.0.
  • Incremented the app’s build number for the new release.

[coderabbitai]

Warning

Review limit reached

@kwsantiago, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: ac15aa04-a691-46a7-b4c1-b1a4fd0926fa

📥 Commits

Reviewing files that changed from the base of the PR and between 863d2de and 8f6e939.

📒 Files selected for processing (10)

• fastlane/metadata/android/de-DE/changelogs/282.txt
• fastlane/metadata/android/de-DE/changelogs/284.txt
• fastlane/metadata/android/en-US/changelogs/282.txt
• fastlane/metadata/android/en-US/changelogs/284.txt
• fastlane/metadata/android/es-ES/changelogs/282.txt
• fastlane/metadata/android/es-ES/changelogs/284.txt
• fastlane/metadata/android/ja-JP/changelogs/282.txt
• fastlane/metadata/android/ja-JP/changelogs/284.txt
• fastlane/metadata/android/pt-BR/changelogs/282.txt
• fastlane/metadata/android/pt-BR/changelogs/284.txt

Walkthrough

The Android app version changed from 1.1.9 (code 27) to 1.2.0 (code 28). The pinned version identifier in keep.version also changed.

Changes

Release update

Layer / File(s)	Summary
Update release metadata and pin app/build.gradle.kts, keep.version	The app version changed to 1.2.0 with version code 28. The pinned version identifier changed to b06b61f71971a3fadc4acca1f340719138d4f8b8.

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

Possibly related PRs

• privkeyio/keep-android#465: Updates the same release version fields and pinned hash.
• privkeyio/keep-android#398: Uses the same release-bump pattern.
• privkeyio/keep-android#299: Updates app release metadata and the pinned version hash.

Suggested reviewers: wksantiago

Poem

A rabbit checked the version line,
And saw a fresh release sign.
The code rose up, the pin moved too,
From old identifiers to new.
Hop, hop—the build is ready to go!

🚥 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 version release and the keep pin update, which are the main changes in the pull request.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-v1.2.0

---

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