**This is an automatic release.**

## RevenueCat SDK
### ✨ New Features
* WEB-3903: Stripe Checkout branding support (#828) via Nicola Sacco
(@nicfix)

## RevenueCatUI SDK
### ✨ New Features
* PW-1201 | Bump `purchases-ui-js` package to enable promo text
overrides for discounts (#832) via Rosie Watson (@RosieWatson)

### 🔄 Other Changes
* Refactor checkoutStart/postCheckoutStart to use params objects (#825)
via Volodymyr Kartavyi (@vkartaviy)
* Fix package.json to reflect correct version (#824) via Toni Rico
(@tonidero)
* Merge release PR after deploy (#812) via Antonio Pallares
(@ajpallares)

## Summary

Adds two complementary guardrails so contributors can't accidentally
modify the version manually, and so drift between the three version
sources (`.version`, `package.json`, `src/helpers/constants.ts`) is
caught in CI:

- **Danger rule** (local `Dangerfile`) — fails PRs that touch the
`version` line in `package.json`, `.version`, or
`src/helpers/constants.ts` when the head branch is **not** `release/*`.
Error message points contributors to `bundle exec fastlane bump`.
- **CI consistency check** — new step in the existing `test` job (`pnpm
run check-version-consistency`) runs
`scripts/check-version-consistency.mjs`, which reads the three files and
fails if they disagree. Runs regardless of branch, so it also catches
drift on release branches.

The Fastlane `bump` lane already updates all three files atomically via
the `files_with_version_number` map in `fastlane/Fastfile`, so no
changes are needed on the release side.

### Why

Contributors have occasionally edited `package.json`'s `version`
directly in feature PRs (historical examples around PRs #824 / #835),
thinking that's how releases are cut. That causes drift from `.version`,
which is Fastlane's source of truth.

## Test plan

- [ ] CI: `danger` job passes on this PR (no version lines touched).
- [ ] CI: `test` job's new "Check version consistency" step passes on
this PR.
- [ ] Manual sanity: push a scratch commit that bumps only
`package.json` version → both Danger and the CI step should fail with
the instructive messages. Revert before merging.
- [ ] On a `release/*` branch, the Danger rule should skip (allow the
bump) while the CI consistency step still passes as long as the three
files match.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>