1.8.0

Release Notes for 1.8.0

Added

• The action now detects Codeception configuration, and, when found, adds a matrix item for running Codeception tasks.

Changed

• The generated matrix now only adds unit tests against locked dependencies for the lowest supported PHP version. (Unit test runs against lowest and latest dependencies are still performed for all PHP versions the package supports.)

• For non-unit test CI items in the matrix that previously tested against the default "stablePHP", if no "stablePHP" is defined in the package CI configuration, the lowest supported PHP version for the package is used. Previously, we used a static version (defined currently at 7.4) for all repositories.

  This means that:

  • Maintainers will need to ensure the Composer lockfile is created against the lowest supported PHP version for the given release branch.
  • OR that the package CI configuration defines a "stablePHP" value indicating the specific PHP version they wish to run non-unit test tooling against.

• The action now performs schema validation against discovered composer.json files, failing the job if the composer.json is invalid.

1.8.0

• Total issues resolved: 1
• Total pull requests resolved: 3
• Total contributors: 2

Enhancement

• 35: Execute phpunit with locked version only on the minimum supported PHP version of a project thanks to @boesing
• 34: Codeception checks thanks to @boesing
• 33: feature: introduce composer.json schema validation thanks to @boesing and @Slamdunk

1.7.1

Release Notes for 1.7.1

Fixed

• This release fixes an issue that occurs when the branch used to create the patch has the same name as the target branch, thus causing a collision during checkout. The action now adds a prefix to the patch branch name to resolve the issue.

1.7.1

• Total issues resolved: 0
• Total pull requests resolved: 1
• Total contributors: 1

Bug

• 29: Ensure pull request branch name does not cause collisions thanks to @weierophinney

1.7.0

Release Notes for 1.7.0

Added

• This release adds a new key to jobs it emits, "ignore_platform_reqs_8", with a boolean value, defaulting to true. The flag is used to indicate whether or not the --ignore-platform-req=php flag should be passed to composer update and composer install commands.

1.7.0

• Total issues resolved: 0
• Total pull requests resolved: 1
• Total contributors: 1

Enhancement

• 28: Allow toggling --ignore-platform-reqs option on PHP 8.0 thanks to @weierophinney

1.6.0

Release Notes for 1.6.0

Changed

• When no jobs are detected, the "no-op" job created now results in an empty "command" item, instead of one that performs an "echo" statement. laminas-continuous-integration-action now correctly detects an empty "command" and acts as a no-op in that scenario.

1.6.0

• Total issues resolved: 0
• Total pull requests resolved: 1
• Total contributors: 1

Enhancement

• 27: feat: use empty command for no check thanks to @boesing

1.5.2

Release Notes for 1.5.2

1.5.x bugfix release (patch)

1.5.2

• Total issues resolved: 1
• Total pull requests resolved: 0
• Total contributors: 1

Bug

• 23: Fix broken v1 tag thanks to @weierophinney

1.5.1

Release Notes for 1.5.1

1.5.1

• Total issues resolved: 0
• Total pull requests resolved: 1
• Total contributors: 1

Bug

• 20: Fix tag concatenation in build-and-push-containers workflow input thanks to @weierophinney

1.5.0

Release Notes for 1.5.0

Changed

• This release adds the --no-cache flag when running Psalm checks.

1.5.0

• Total issues resolved: 0
• Total pull requests resolved: 2
• Total contributors: 2

Enhancement

• 18: qa: do not use psalm cache thanks to @boesing
• 17: Simplify workflow for building container thanks to @weierophinney

1.4.0

Release Notes for 1.4.0

Changed

• This release updates the entrypoint for the container backing the action to allow usage with actions/checkout if desired, or to use the container in a local checkout without requiring a new cloning operation.

1.4.0

• Total issues resolved: 1
• Total pull requests resolved: 1
• Total contributors: 1

Enhancement

• 16: Update entrypoint to allow usage with actions/checkout thanks to @weierophinney

1.3.0

Release Notes for 1.3.0

Added

• Adds the ability to specify the key additional_checks, containing an array of additional checks to perform beyond those auto-discovered by the tool.
  See the documentation for further details.

Changed

• You can now specify individual jobs in the "checks" configuration as objects, instead of only as a JSON string. When specified in this way, the action will cast the job to a JSON string for you.

• The action now performs validations on each element of the "checks" configuration, raising warnings for anything malformed, and omitting those particular checks.

1.3.0

• Total issues resolved: 2
• Total pull requests resolved: 2
• Total contributors: 1

Enhancement

• 14: Allow object jobs in the "checks" configuration array thanks to @weierophinney
• 13: Provide ability to specify jobs defined in checks configuration as objects thanks to @weierophinney
• 12: Provide ability to provide checks to run in addition to auto-discovered checks thanks to @weierophinney

1.2.3

Release Notes for 1.2.3

1.2.x bugfix release (patch)

1.2.3

• Total issues resolved: 0
• Total pull requests resolved: 1
• Total contributors: 1

Bug

• 9: Fix name of image to generate in build-and-push-containers workflow thanks to @weierophinney