v2.0.0

Added

• Support for VIP Local Development Environment

Changed

• Modernize codebase for PHP 8, Composer v2.4 (removed support for PHP 7 and Composer < v2.4)
• Refactored production autoload relying more on Composer
• Improved TaskConfig
• Improved Config validation
• Improved and made public DownloadWpCore::normalizeWpVersion
• Add support for custom env config files in 'vip-composer-plugin-env-config' packages
• Git URL and Branch in task config aren't mandatory
• QA improvements
  • Split unit tests workflow to use Composer version in the matrix
  • Make use of Inpsyde reusable workflows
  • Improved and modernized code styles and static analysis

v1.6.0

Added

• Support for Composer packages of type "vip-composer-plugin-env-config" to hold configuration files

Fixed

• Improved compatibility with Composer 2.5.4+

v1.5.3

Fixed

• PHP 8.1 & 8.2 support - props @Chrico
• Fix Psalm check failing QA checks - props @gmazzap
• Document the "support table" for PHP/Composer versions: older Composer versions (1, 2.0) are not supported on most recent PHP versions (8.1, 8.2) - props @gmazzap

v1.5.2

Added

• Autoload for supporting MU plugins (props @remyvv, see #8)

Fixed

• QA refresh for updated Psalm

v1.5.1

Fixed

• Enable any kind of file in the /languages folder. At least, json was required, but no real reason to limit other file types.

v1.5.0

Fixed

• Added compatibility with Composer v2.3 by changing the generated production autoload

Changed

• Refactor QA workflow and refreshed CS in files to coiunt for updated tools changes.

v1.4.0

Changed

• VIP Go MU plugins are now pulled from the "built" repository (instead of recursively via gitmodules)

1.3.4

Remove `composer.json` from the bacllist of copied files

We experienced some cases where the `composer.json` file was needed for the correct behavior of the plugins or themes deployed. So, waiting for a more structured way to include or exclude files, we just keep deploying again `composer.json` files.