Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion VERSION
Original file line number Diff line number Diff line change
@@ -1 +1 @@
9.20.2
9.20.3
2 changes: 1 addition & 1 deletion composer.json
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
"name": "adyen/module-payment",
"description": "Official Magento2 Plugin to connect to Payment Service Provider Adyen.",
"type": "magento2-module",
"version": "9.20.2",
"version": "9.20.3",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The version number is also specified in the root VERSION file. Having the version number defined in multiple places can lead to inconsistencies if one is updated and the other is missed. To improve maintainability and adhere to the DRY (Don't Repeat Yourself) principle, it would be beneficial to establish a single source of truth for the version number. Since the application reads the version from this file (via Helper\Data::getModuleVersion()), composer.json appears to be the effective source of truth. A release script could be used to automatically generate or update the VERSION file from this one to ensure they remain synchronized.

"license": "MIT",
"repositories": [
{
Expand Down
Loading