chore(deps): bump flymoon-payment-api 1.0.20260520 (LES-1184)
Code Review on payment MR !87 caught that fly_moon_admin's master pom still pins flymoon-payment-api 1.0.20260316.1001 — older than the v162 agent's 1.0.20260508 and missing trial enum entirely. Once the new payment provider rolls (with WriteEnumsUsingName), admin's Dubbo consumer of AgentUserPointsService would silently get subscriptionType=null whenever a trial user's record is fetched (fastjson2 JSONB returns null for unknown enum names instead of throwing; ordinal=2 from rolling provider would also throw on this old jar).
Bumping to 1.0.20260520 brings admin onto the same payment-api contract as the rest of the squad. New jar:
- Contains SubscriptionTypeEnum.trial (ordinal 2)
- @JSONType(serializeFeatures = WriteEnumsUsingName) — wire is "trial" / "monthly" / "annually"
- Custom StrictReader rejects unknown names + out-of-range ordinals with JSONException (covers Dubbo JSONB binary path)
Cross-repo coordination
| repo | <flymoon-payment-api.version> | branch / MR |
|---|---|---|
| fly_moon_payment | 1.0.20260520 | sit_0519 ← MR !87 |
| fly_moon_agent | 1.0.20260520 | sit_0519 ← MR !96 |
| fly_moon_admin | 1.0.20260520 | master ← THIS MR |
Per Reviewer guidance, this MR ships in the same window as !87 / !96. Deploy ordering decision belongs to Archiver.
Verification: mvn -B clean compile passes against locally-installed 1.0.20260520. No source code changes required — the API surface is backward compatible, AgentUserPointsController#userPointsService @DubboReference signature unchanged.
Agent-Task-Id: 20260520-2fc134-p1