Merge release 1.26.0 into 2.0.x #302
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
This fixes the problem that the job name does not match for tools due to the fact that the name already contains the human-readable name containing the version and dependencies string. Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
The exclusion strategy, when it was introduced, was meant to handle exact job names. By having the new feature of excluding tool names as well, we should still support the fill job.name as well so that we can still properly exclude jobs based on the initial exclusion strategy. Signed-off-by: Maximilian Bösing <[email protected]>
…iguration` Signed-off-by: Maximilian Bösing <[email protected]>
With one of the newer versions of the matrix action, `test.env` files were introduced and thus have to be added to the new test cases as well. Signed-off-by: Maximilian Bösing <[email protected]>
This allows us to reference to that definition which eases the usage in several parts of the configuration. Having the list of supported PHP versions maintained in more than one location may become annoying and thus this changes makes a lot of sense. Signed-off-by: Maximilian Bösing <[email protected]>
This was introduced in a more recent matrix version and thus was missing the expected matrix from the initial version of this feature. Signed-off-by: Maximilian Bösing <[email protected]>
… from `.laminas-ci.json` reflects proper PHP version Signed-off-by: Maximilian Bösing <[email protected]>
Stable PHP should represent an actual PHP version and thus `lowest` and `latest` or even wildcard references make no sense. Signed-off-by: Maximilian Bösing <[email protected]>
… `php` enum values Signed-off-by: Maximilian Bösing <[email protected]>
… match, not `all` Signed-off-by: Maximilian Bösing <[email protected]>
…d `php` specific enum strings Signed-off-by: Maximilian Bösing <[email protected]>
Signed-off-by: Maximilian Bösing <[email protected]>
Due to the fact that there is no `composer.lock` file available, the matrix will not generate any `locked` jobs. Signed-off-by: Maximilian Bösing <[email protected]>
…cies Extend `exclude` with `php` and `dependencies` settings
…to-2.0.x_jlRhIfXc
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release Notes for 1.26.0
1.26.0
Enhancement
excludewithphpanddependenciessettings thanks to @boesing