Release 5.7.0

[kherembourg]

Summary

• Bump Flutter SDK version to 5.7.0
• Update iOS Purchasely SDK from 5.6.4 to 5.7.0
• Update Android Purchasely SDK from 5.6.0 to 5.7.0 (core, google-play, player)
• Update bridge version in iOS and Android native plugins
• Update VERSIONS.md and changelogs

Files changed

• purchasely/pubspec.yaml, purchasely_google/pubspec.yaml, purchasely_android_player/pubspec.yaml — version bump
• purchasely/ios/purchasely_flutter.podspec — iOS SDK 5.7.0
• purchasely/android/build.gradle, purchasely_google/android/build.gradle, purchasely_android_player/android/build.gradle — Android SDK 5.7.0
• SwiftPurchaselyFlutterPlugin.swift, PurchaselyFlutterPlugin.kt — bridge version 5.7.0
• VERSIONS.md — new version row
• All CHANGELOG.md files — 5.7.0 entry

Test plan

• flutter test — 261 tests passed
• flutter analyze lib/ — no issues
• pod update — Purchasely 5.7.0 resolved
• CI passes

[gemini-code-assist]

Summary of Changes

Hello @kherembourg, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on a significant version upgrade for the Purchasely SDK across all supported platforms. It updates the core Flutter SDK, along with its iOS and Android native components, to version 5.7.0. This ensures the project leverages the latest features, bug fixes, and performance improvements provided by the updated SDK, maintaining compatibility and enhancing the overall stability of the integration.

Highlights

• Flutter SDK Version Bump: The Flutter SDK version has been updated to 5.7.0.
• iOS Purchasely SDK Update: The iOS Purchasely SDK has been updated from version 5.6.4 to 5.7.0.
• Android Purchasely SDK Update: The Android Purchasely SDK (core, google-play, player) has been updated from version 5.6.0 to 5.7.0.
• Bridge Version Alignment: The bridge version in both iOS and Android native plugins has been updated to 5.7.0 to match the new SDK versions.
• Documentation and Changelog Updates: The VERSIONS.md file and all CHANGELOG.md files have been updated to reflect the new 5.7.0 release.

Changelog

• VERSIONS.md
  • Added a new entry for version 5.7.0, aligning native SDK versions.
• purchasely/CHANGELOG.md
  • Added a new changelog entry for version 5.7.0, including a link to the full changelog.
• purchasely/android/build.gradle
  • Updated the io.purchasely:core dependency from 5.6.0 to 5.7.0.
• purchasely/android/src/main/kotlin/io/purchasely/purchasely_flutter/PurchaselyFlutterPlugin.kt
  • Updated the sdkBridgeVersion string to '5.7.0'.
• purchasely/example/ios/Podfile.lock
  • Updated the Purchasely dependency to 5.7.0 and regenerated checksums.
• purchasely/example/pubspec.lock
  • Updated the purchasely_flutter package version to 5.7.0.
• purchasely/ios/Classes/SwiftPurchaselyFlutterPlugin.swift
  • Updated the sdkBridgeVersion string to '5.7.0'.
• purchasely/ios/purchasely_flutter.podspec
  • Updated the Purchasely dependency to 5.7.0.
• purchasely/pubspec.yaml
  • Updated the package version to 5.7.0.
• purchasely_android_player/CHANGELOG.md
  • Added a new changelog entry for version 5.7.0, including a link to the full changelog.
• purchasely_android_player/android/build.gradle
  • Updated the io.purchasely:player dependency from 5.6.0 to 5.7.0.
• purchasely_android_player/pubspec.yaml
  • Updated the package version to 5.7.0.
• purchasely_google/CHANGELOG.md
  • Added a new changelog entry for version 5.7.0, including a link to the full changelog.
• purchasely_google/android/build.gradle
  • Updated the io.purchasely:google-play dependency from 5.6.0 to 5.7.0.
• purchasely_google/pubspec.yaml
  • Updated the package version to 5.7.0 and the purchasely_flutter dependency to 5.7.0.

Activity

• No human activity (comments, reviews, etc.) has been recorded on this pull request yet.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request correctly bumps the version to 5.7.0 across all relevant files. The changes are consistent and reflect the summary provided. I've added a few suggestions to improve the changelogs for better developer experience by making them more descriptive. I also found some code style inconsistencies regarding indentation in both the Swift and Kotlin plugin files, for which I've suggested fixes. Overall, this is a solid release preparation.