1.19.0

Remote update plans without weakening active requirements

• Keep the current requirement while announcing additional timed scheduledRequirements. The strictest active minimum applies, including when plans overlap; ending or removing a plan leaves the active baseline in force.
• Retain and reevaluate plans across restarts with the existing immutable revisions and bounded policy/publication evidence. A future unpublished version does not invalidate sufficient publication evidence for the current minimum.
• Add MHRemoteConfigSection<Value> so missing or invalid feature payloads remain observable without discarding valid siblings from one shared response. Broken JSON, envelope/identity failures, and cancellation still reject the shared request. Failed update sections cannot renew retained update evidence.

Compatibility and adoption

• Standard endpoint/Store-ID initialization, lifecycle preparation, and operation checks are unchanged. Existing schedule/feature initializers, 1.18.0 documents, and retained snapshots remain supported.
• Deploy this reader before relying on scheduledRequirements: older readers ignore the new field and enforce only the baseline. Keep that baseline when announcing plans. Clear both the baseline and all plans, with a higher revision, for full cancellation.
• No announcement feature or additional app-side plan-selection/recovery machinery is introduced.

See the remote update adoption guide for the wire format, failure boundaries, and rollout order.

Full changelog