Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge release 1.26.0 into 2.0.x #302

Merged
merged 19 commits into from
May 5, 2024
Merged

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented May 5, 2024

Release Notes for 1.26.0

1.26.0

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

Enhancement

boesing added 19 commits May 5, 2024 15:45
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
…iguration`

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
… from `.laminas-ci.json` reflects proper PHP version

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
… `php` enum values

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
… match, not `all`

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
…d `php` specific enum strings

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
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 <2189546+boesing@users.noreply.github.com>
…cies

Extend `exclude` with `php` and `dependencies` settings
@boesing boesing merged commit 9f142ec into 2.0.x May 5, 2024
45 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant