Originally created by: Akarsh-Hegde
Arms the mandatory-update floor on the staging channel to verify enforce_minimum_version end-to-end before we ever need it in a real rollback (RUNBOOK.md §A2).
Adds tray/minimum-version = 1.71.0. At release time scripts/package-updater.sh reads it and bakes a Minimum-Version: 1.71.0 line into latest.json's notes (the notes body is the transport because tauri-plugin-updater drops unknown manifest fields), and mirror-staging-release.sh copies that manifest verbatim onto the rolling updater-staging channel.
Staging builds are prereleases (1.71.0-staging.N), and semver puts every one of them below 1.71.0 — so installed staging apps below the floor force-install via update::enforce_minimum_version with no consent click, checked 30 s after launch and every 6 h thereafter.
1.71.0 is the highest floor this release can legally carry: package-updater.sh compares cores only and fails the release loudly if the floor exceeds the release version.
Patching latest.json on the updater-staging release would exercise only the app half. This path additionally covers package-updater.sh's file read and floor-vs-version guard, and the mirror script's notes propagation — the parts most likely to bite during an actual emergency rollback.
Squash-merge this PR (do not use a merge commit). Two things must both be true of the resulting commit on pre-main:
[staging-release] — release-staging.yml only builds on that marker, never on ordinary integration pushes.commit-analyzer runs the conventionalcommits preset with no custom releaseRules, so only feat/fix/perf/revert/breaking cut a release. A test: or chore: commit would trigger the workflow and then publish nothing after a ~45 min build.The PR title satisfies both, and GitHub defaults the squash-commit message to it. A merge commit would re-expose risk [#2] by putting the original test(update): commit on the branch.
On a staging machine running below 1.71.0-staging.6, relaunch the app:
meridian logs --service meridian-tray -f → update: running version is below the minimum supported - forcing installEmpty tray/minimum-version in a follow-up PR once propagation is confirmed. The floor ships with every release while the file has content, and pre-main promotes to main — leaving it armed would force-update production users on the next release.
🤖 Generated with Claude Code
Originally posted by: coderabbitai[bot]
✨ Finishing Touches
🧪 Generate unit tests (beta)
- [ ] Create PR with unit tests - [ ] Commit unit tests in branch `test/minimum-version-floor`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](https://twitter.com/intent/tweet?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A&url=https%3A//coderabbit.ai) - [Mastodon](https://mastodon.social/share?text=I%20just%20used%20%40coderabbitai%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20the%20proprietary%20code.%20Check%20it%20out%3A%20https%3A%2F%2Fcoderabbit.ai) - [Reddit](https://www.reddit.com/submit?title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&text=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code.%20Check%20it%20out%3A%20https%3A//coderabbit.ai) - [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcoderabbit.ai&mini=true&title=Great%20tool%20for%20code%20review%20-%20CodeRabbit&summary=I%20just%20used%20CodeRabbit%20for%20my%20code%20review%2C%20and%20it%27s%20fantastic%21%20It%27s%20free%20for%20OSS%20and%20offers%20a%20free%20trial%20for%20proprietary%20code)Comment
@coderabbitai helpto get the list of available commands.Ticket changed by: Akarsh-Hegde