**This is an automatic release.**

## RevenueCat SDK
### ✨ New Features
* Unified StoreReplacementMode API (RevenueCat#3234) via Will Taylor
(@fire-at-will)
* Add placement and targeting context to paywall events (RevenueCat#3253) via Dan
Pannasch (@dpannasch)
### 🐞 Bugfixes
* Fix null Placements when offering_ids_by_placement is absent (RevenueCat#3254)
via Dan Pannasch (@dpannasch)

## RevenueCatUI SDK
### Paywallv2
#### ✨ New Features
* Wire multipage workflow navigation into PaywallViewModel (RevenueCat#3381) via
Cesar de la Vega (@vegaro)

### 🔄 Other Changes
* Add `triggerType` to `WorkflowTrigger` (RevenueCat#3393) via Cesar de la Vega
(@vegaro)
* Extract private function `NavigateTo.toPaywallAction` (RevenueCat#3392) via
Cesar de la Vega (@vegaro)
* Bump revenucatui-tests gradle cache key (RevenueCat#3391) via Toni Rico
(@tonidero)
* Create `WorkflowTriggerType` and `WorkflowTriggerActionType` (RevenueCat#3386)
via Cesar de la Vega (@vegaro)
* Update baseline profiles (RevenueCat#3390) via RevenueCat Git Bot (@RCGitBot)
* Plumb `componentId` through buttons on workflow interactions (RevenueCat#3380)
via Cesar de la Vega (@vegaro)
* Add `ButtonComponent.Action.Workflow` (RevenueCat#3385) via Cesar de la Vega
(@vegaro)
* Add `componentId` to `ButtonCoomponentStyle` (RevenueCat#3384) via Cesar de la
Vega (@vegaro)
* Migrate all suspendCoroutine usages to suspendCancellableCoroutine
(RevenueCat#3365) via Jaewoong Eum (@skydoves)
* Add `WorkflowNavigator` for multipage workflow step navigation (RevenueCat#3379)
via Cesar de la Vega (@vegaro)
* build(deps): bump fastlane-plugin-revenuecat_internal from `b822f01`
to `d24ab26` (RevenueCat#3383) via dependabot[bot] (@dependabot[bot])
* Add `id` field to `ButtonComponent` (RevenueCat#3377) via Cesar de la Vega
(@vegaro)
* Add CI workflows for generating Baseline Profiles (RevenueCat#3372) via Jaewoong
Eum (@skydoves)
* add min sdk level for paywalls and customer center (RevenueCat#2465) via
Muhammad-Sharif Moustafa (@mshmoustafa)

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Low risk release bookkeeping: updates version strings, changelogs, and
documentation deployment targets without changing runtime logic beyond
the reported version identifier.
> 
> **Overview**
> Cuts the `10.3.0` release by updating all version references from
`10.3.0-SNAPSHOT` to `10.3.0` across build config (`gradle.properties`,
`.version`, `Config.frameworkVersion`) and sample/test app dependency
pins.
> 
> Updates release documentation publishing to sync Dokka output to the
`10.3.0` S3 path and changes `docs/index.html` to redirect to `10.3.0`.
Also promotes release notes by moving `CHANGELOG.latest.md` entries into
a new `CHANGELOG.md` section for `10.3.0`.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
056ce62. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

## Summary
- Include `placement_identifier`, `targeting_revision`, and
`targeting_rule_id` in paywall events under a
`presented_offering_context` nested object
- Field is omitted when no placement or targeting data exists
- Consistent with iOS and Android implementations

## Related PRs
- iOS: RevenueCat/purchases-ios#6476
- Android: RevenueCat/purchases-android#3253

## Test plan
- [x] Unit tests for all context permutations (full, placement-only,
targeting-only, none, empty string)
- [x] JSON round-trip serialization tests
- [x] Integration test verifying context flows from offering to event
payload
- [x] Manual testing with targeting rules and placements in demo app

)

### Description

Adds `placement_identifier`, `targeting_revision`, and
`targeting_rule_id` to the custom paywall impression event.

Mirrors the event payload work in iOS PR
RevenueCat/purchases-ios#6707 for Android. The
internal paywall events already received this context via RevenueCat#3253; this PR
brings the same placement/targeting attribution to custom paywall
events.

### What's new

- `CustomPaywallImpressionParams` gains an `Offering`-based constructor.
Passing an `Offering` lets the SDK derive the offering identifier and
`PresentedOfferingContext` from the offering's first available package.
- The params object stores `paywallId`, `offeringId`, and
`presentedOfferingContext`; it does not store or expose the `Offering`
object. This keeps the public params surface focused on the values
needed for event tracking.
- The string `offeringId` constructor is deprecated in favor of passing
an `Offering`, because an offering identifier alone cannot reliably
carry placement and targeting context.
- An `@InternalRevenueCatAPI` constructor accepts `paywallId`,
`offeringId`, and `presentedOfferingContext` directly, so hybrid SDKs
can pass the context through PHC to native without exposing `Offering`
on the public params API.
- `Purchases.trackCustomPaywallImpression(params)` resolves event data
with this fallback chain:

  | Developer passes | `offering_id` sent | context sent |
  | --- | --- | --- |
| Nothing (or only `paywallId`) | from `cachedOfferings.current` | from
current offering |
| Deprecated `offeringId` matching cache | passed string | from cached
match |
  | Deprecated `offeringId` not in cache | passed string | nil |
  | `Offering` object | from offering | derived from offering |
| Internal `presentedOfferingContext` | passed `offeringId` | passed
context |

- `CustomPaywallEvent.Impression.Data` carries flat
`placementIdentifier` / `targetingRevision` / `targetingRuleId` fields,
mirroring the existing internal `PaywallEvent` Android shape.
- The wire payload nests these under `presented_offering_context`. The
custom paywall event has its own
`BackendEvent.CustomPaywallPresentedOfferingContextData` rather than
reusing the internal paywall event's struct, matching the iOS approach
where each event owns its own.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Medium Risk**
> Public API surface changes (new constructors, deprecation) and
analytics event schema updates; behavior is localized to custom paywall
tracking rather than purchases or auth.
> 
> **Overview**
> Custom paywall impression tracking now sends **placement and targeting
context** (placement identifier, targeting revision, rule id) on the
backend event, nested as `presented_offering_context`, aligning custom
paywalls with internal paywall analytics.
> 
> **`CustomPaywallImpressionParams`** adds constructors that take an
**`Offering`** (or offering-only) so the SDK can set `offeringId` and
`presentedOfferingContext` from the offering’s first package. The
**`offeringId` string constructor is deprecated** in favor of
`Offering`. Params expose `presentedOfferingContext` but not the
offering object itself.
> 
> **`Purchases.trackCustomPaywallImpression`** resolves what gets
tracked: explicit context from params, lookup from **cached offerings**
when only an offering id or nothing is passed, or values taken directly
from a passed **`Offering`**.
> 
> Wire and storage paths extend **`CustomPaywallEvent.Impression.Data`**
and **`BackendEvent.CustomPaywall`** with the new fields;
**`cachedOfferings`** is exposed on the orchestrator/offerings manager
to support resolution.
> 
> <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit
ea3369c. Bugbot is set up for automated
code reviews on this repo. Configure
[here](https://www.cursor.com/dashboard/bugbot).</sup>
<!-- /CURSOR_SUMMARY -->