Phala Pay 0.9.2

Fixed

• Chainlink sources omitting rpc_group_b with rpc_group: a when the route's second RPC group is
  literally a (e.g. ["x", "a"]) previously read one group twice, silently losing A/B
  independence. Upgrading reads two independent groups and may newly reject quotes as divergent.
  Configurations setting rpc_group_b explicitly are unaffected and need no action.
• Sequencer uptime validation now checks the groups the service reads; previously it looked up
  a/b literally while the service resolved them as route aliases. Runtime is unchanged.
  Configurations that only validated under the old lookup may now be rejected by config check.
  Shipped staging, example, and examples/ configurations use non-alias sequencer group names and are
  unaffected.

Python SDK (phala-pay)

Changed

• The 60 resource method signatures that previously declared request_deadline and
  upgrade_tolerance now show **options in help() and inspect.signature(); the accepted
  runtime keywords are unchanged. Unknown-keyword TypeError messages no longer include the
  method name prefix.

Deprecated

• The legacy PhalaPay constructor is deprecated and emits DeprecationWarning; it will be
  removed in 0.10.0. Configure pins or use PhalaPay.from_env() instead.

SDKs

@phala/pay 0.9.2, @phala/pay-react 0.9.2, and @phala/pay-server 0.9.2 on npm;
phala-pay 0.9.2 on PyPI.

Verify

deploy/verify-release.sh
checks this release as Deploy does (self-hosting guide).