fix(flutter): validate Apple release paths

[hyochan]

Summary

• validate the Flutter release with the CocoaPods fallback on Flutter 3.41/Xcode 16
• add a separate Flutter 3.44/Xcode 27 SwiftPM release gate
• block publication until both Apple integration paths pass
• synchronize the docs metadata for the already released React Native 16 and Expo 5 packages

Context

The first Flutter 10.0.0 release attempt stopped before versioning or publication because Flutter 3.41 generated an iOS 13 SwiftPM consumer for a package whose new minimum is iOS 15. This keeps that toolchain on its supported CocoaPods fallback while validating the documented Flutter 3.44+ SwiftPM path separately.

Verification

• bun run audit:parity
• bun run audit:docs
• bun run audit:release-state
• Prettier, YAML parse, and git diff --check

Summary by CodeRabbit

• Bug Fixes

  • Improved Apple release validation to support both Swift Package Manager and CocoaPods configurations, including lockfile-based CocoaPods checks.
  • Strengthened verification for Flutter-based Apple consumer builds.

• New Features

  • Added a dedicated SwiftPM validation job for Apple consumer examples and wired it into the main deploy flow.

• Documentation

  • Updated installation examples to reference OpenIAP version 3.0.0.

• Tests / Chores

  • Updated release-branch policy assertions to match new guarded dependency expectations.

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

[coderabbitai]

📝 Walkthrough

Walkthrough

The release Flutter workflow now validates CocoaPods fallback and SwiftPM Apple consumer builds before deployment. The parity audit and release policy test enforce the updated workflow coverage, while native installation documentation references version 3.0.0.

Changes

Flutter release validation

Layer / File(s)	Summary
Release workflow validation .github/workflows/release-flutter.yml	The iOS job disables SwiftPM, installs CocoaPods dependencies, verifies openiap in Podfile.lock, and adds an Xcode 27 SwiftPM consumer-build job required by deployment.
Parity and release contract updates scripts/audit-non-godot-parity.mjs, scripts/release-branch-policy.test.mjs	Parity checks cover both Flutter workflows, dependency-manager settings, SwiftPM job wiring, and the updated xcode_version extraction; the release policy test expects three guarded Flutter jobs.
Native installation version updates packages/docs/public/llms*.txt	Native iOS/macOS and Android dependency examples are updated to version 3.0.0, with generated timestamps refreshed.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant validate-ios
  participant validate-apple-swiftpm
  participant deploy
  validate-ios->>validate-ios: Verify CocoaPods fallback and openiap pod
  validate-apple-swiftpm->>validate-apple-swiftpm: Build Apple SwiftPM consumer
  validate-ios-->>deploy: Validation passes
  validate-apple-swiftpm-->>deploy: Validation passes
  deploy->>deploy: Proceed after both validations

Loading

Possibly related PRs

• hyodotdev/openiap#161: Added related SwiftPM integration and parity-audit expectations for Flutter Apple builds.

Suggested labels: 🧪 test, 📘 release, 📖 documentation

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately summarizes the main change: validating Flutter Apple release paths.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/flutter-release-apple-validation

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}