v4.0.0

Important note about versioning

In this release, GitHub have changed to an auto-tagging model, where the release will be made as vX.Y.Z and an automatic tag is created called vX, so there will be no more proxy releases for the latest version number - just use v4 from now on!

What's Changed

• support --coverage-filter flag by @shish in #60
• Use composer version of PHPUnit by default if availble by @g105b in #61
• Revert phpbuild (docker user) by @g105b in #63
• Remove the default value for the test_suffix parameter by @cookieguru in #64

New Contributors

• @shish made their first contribution in #60
• @cookieguru made their first contribution in #64

Full Changelog: v3.0.3...v4

Brought configuration options up to date

The latest PHPUnit v10 release introduced some new configuration options, and this Github Action was missing some options relating to Coverage generation. These have now been added and documented in the README file.

February 2023

v3

February 2023

v3.0.2

This minor patch release introduces coloured ANSI output in the Actions terminal viewer.

v3.0.1

What's Changed

• Add option to point to a vendored phpunit executable by @blackwolf12333 in #44
• Tidy merge conflicts by @g105b in #48
• Improve deprecated Actions output

New Contributors

• @blackwolf12333 made their first contribution in #44

Full Changelog: v3...v3.0.1

v3.0.0

Thank you for your interest in php-actions. I'm happy to be making a new release that introduces the following improvements:

• The host environment variables within Github Actions are passed to the Docker container. This Action runs as a Composite Runner, so the actual tests are ran within a custom Docker image, supplied by php-build.
• The host's networking is shared with the Github Action runner. Thanks to @osma for fixing the way that networking is handled within the runner. This is a great improvement.
• When a build fails, all debug output is shown within the action's output, but is grouped within a "debug output" summary. This means that whether your build passes or fails, you'll still see the PHPUnit output in the format you'd expect, but you are now only one click away from viewing all the commands Github Actions ran to get the build running, in case there is a configuration issue to debug. This is shown as the last line of the output, as a clickable summary group that expands to show the full detail.
• Documentation of inputs is brought in sync with default values.

From now on, minor version releases will be made using semantic versioning, with the major version being retagged on the non-specific version tag. For example, the release of v3.0.0 will be tagged as both v3.0.0 and v3 - when a minor version is released, a new tag of v3.1.0 will be created, and the v3 tag will be retagged to point to the latest release within the major release of 3.x. This gives developers the choice of whether to keep up to date with all v3 developments, or fix their builds to a specific version of this action.

As always, have fun and stay productive!

If you've found this action helpful, please consider sponsoring the developer.

Speed improvements and self-owned packages

This release of php-actions/phpunit has tackled speed issues associated with previous versions, while maintaining (and enhancing) the configuration possibilities - you can still choose between PHP version and PHPUnit version, but now you can also choose which PHP extensions are installed for your test runs, making the test runner extremely minimal with only the baseline required components.

Please note, to achieve the build speeds and configuration possibilities, the custom Docker image is pushed to the repository that calls the action. This means that your user or organisation will list the package on the page at https://github.com/{organisation}/packages. This shouldn't have any effect on things, but it's worth knowing about.

Patch release 1st March 2021:
All environment variables from the Github Action host runner are exposed to the docker subcontainer.

Configurable PHP/PHPUnit versions

This release comes with the ability to switch which version of PHP and PHPUnit are running within the action, by passing the php_version and phpunit_version input parameters.

With this change, this action's release version numbering has been reset to v1 to avoid any confusion. Previously, the version of the action was linked directly to the version of PHPUnit that was installed within the action, but that was too limiting.

The previous v6, v7, v8 and v9 releases will still remain available for at least the next 12 months (until November 2021), but after that point it is recommended to use the new versioning system, starting at v1 (this release).

Please see the README for more information. Have fun!