`Compose Multiplatform` subscriptions with `RevenueCat`: one purchase flow for iOS and Android

// related

• #0001

  #0001Infra & SaaSGeekNews3 hours ago

  `GitHub` investigates unauthorized access to internal repositories

  40radar

  Scope is currently limited to internal repositories. No evidence points to customer data outside GitHub repos, so this is a watch item, not an immediate migration trigger.

  • —Confirmed scope is internal repository access. Customer enterprises and organizations are not reported as affected yet.
  • —No evidence currently shows impact to customer information stored outside GitHub internal repos. Keep monitoring official updates.
  • —Practical action is limited: review org audit logs, rotate sensitive tokens if stored carelessly, and avoid panic moves.

  Source: news.hada.io/topic?id=29701Read original →
• #0002

  #0002Infra & SaaSRevenueCat Blog6 hours ago

  `Google Play Billing Library` `9.0`, billing and console updates from I/O 2026

  80radar

  Google Play Billing LibraryAndroid billing library — Google Play in-app purchase integration

  Billing, analytics, protection, and Play Console all moved at once. Android subscription code should be reviewed now, not after a build rejection.

  • —Play Billing Library 9.0.0 is a major version, so billing code deserves a compatibility pass before the next Android release.
  • —The update bundle includes AI, Play Console, analytics, and protection changes. Store operations are expanding beyond payment integration.
  • —RevenueCat coverage matters because it usually translates Google Play billing changes into SDK and migration impact.
  • —Apps with Android subscriptions should watch RevenueCat and Google timelines together. Late migration turns into release risk.

  Source: www.revenuecat.com/blog/engineering/play-billing-v9/Read original →
• #0003

  #0003Infra & SaaSGeekNews7 hours ago

  CISA Contractor Leaked `AWS GovCloud` Keys on GitHub

  40radar

  A public repo exposed high-privilege cloud and internal credentials. Treat secret scanning as a production control, not a checkbox.

  • —The public Private-CISA repo exposed high-privilege AWS GovCloud credentials, plaintext passwords, tokens, and logs.
  • —Default protections that block secret publishing appear to have been disabled; one bad repo setting can bypass the whole safety net.
  • —Immediate takeaway: enforce secret scanning, pre-commit checks, and key rotation even on private or internal repos.

  Source: news.hada.io/topic?id=29689Read original →