Release v10.7.2

[AdyenAutomationBot]

Merged pull requests to be released:

• [ECP-9903] Deprecate buildAdyenTokenizedPaymentRecurringData() method #3242
• [ECP-9906] Remove unused deployment environment assignment #3243
• [ECP-9913] Remove paymentMethod field from donation request #3244
• [ECP-9907] Fix incompatible DB connection pattern in CreateStatusAuthorized class #3246

Full Changelog: v10.7.1...main

[gemini-code-assist]

Summary of Changes

Hello @AdyenAutomationBot, 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 performs a routine version update for the adyen/module-payment Magento 2 module, advancing it to version 10.7.2. This update integrates the changes introduced in the recently merged pull request #3243, ensuring that the module's declared version aligns with the latest codebase.

Highlights

• Version Update: The module version has been incremented from "10.7.1" to "10.7.2" in both the VERSION file and composer.json.
• Included Changes: This release incorporates changes from pull request [ECP-9906] Remove unused deployment environment assignment #3243, which was previously merged into the main branch.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog

• VERSION
  • Updated the module version from 10.7.1 to 10.7.2.
• composer.json
  • Updated the 'version' field from 10.7.1 to 10.7.2.

Activity

• Pull request created by AdyenAutomationBot, indicating an automated release process.
• The PR description links to a full changelog comparing v10.7.1 to main.
• Mentions the inclusion of changes from merged pull request [ECP-9906] Remove unused deployment environment assignment #3243.

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 prepares for the v10.7.2 release by updating the version number in the VERSION and composer.json files. While these changes are correct, a critical update is missing in etc/module.xml. The setup_version attribute is not present in the <module> tag, which is essential for Magento 2's module upgrade process to handle database schema and data migrations. This omission should be addressed to ensure module stability and correct version reporting in the Magento admin.

[gemini-code-assist]

While the version is correctly updated in this file, the corresponding module version in etc/module.xml is missing. For Magento 2 modules, the setup_version attribute in the <module> tag of etc/module.xml is essential for handling database schema and data migrations during upgrades. This attribute appears to be missing entirely from the file.

Please add it, for example:

<module name="Adyen_Payment" setup_version="10.7.2">

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud