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 3.8.1 into 3.9.x #1455

Merged
merged 7 commits into from
Aug 28, 2024
Merged

Conversation

github-actions[bot]
Copy link

Release Notes for 3.8.1

3.8.x bugfix release (patch)

3.8.1

  • Total issues resolved: 0
  • Total pull requests resolved: 4
  • Total contributors: 3

Static Analysis

Tests

Bug

greg0ire and others added 7 commits August 27, 2024 18:03
The pattern is not dynamic, and we know it works. This addresses an
issue reported by PHPStan.
I'm a bit undecided on what's the best way of doing this. Let's at least
use the same strategy everywhere we can.
Be consistent with how we deal with preg_match's return type
These extra tests may help in the future to catch unintended behavior changes for the default of these 2 specific settings.
As result of some past changes to improve the way the option was inferred, several attempts to build a mechanism to handle the absence of value of this option were built via the following commits:

4da00c5
5335951
5038099
799f16d
f726a5f

This commit leverages all the iterative improvements introduced along the way, and setting the correct value when the option is correctly specified.

This should bring the behavior inline with what is currently documented, while additionally adding a documentation deprecation informing users that passing a value to that option won't be allowed in 4.x

As an extra addition, this commit also introduces the negated option `--no-all-or-nothing`. The intent is to leverage the native Symfony >= 5.3 [Negatable command options](https://symfony.com/blog/new-in-symfony-5-3-negatable-command-options) in the future once the optional value from `--all-or-nothing` is completely removed.
GH-1443: Fix default option when `--all-or-nothing` option is used as intended
@derrabus derrabus merged commit 610092c into 3.9.x Aug 28, 2024
14 checks passed
@derrabus derrabus deleted the 3.8.x-merge-up-into-3.9.x_GRxzps5b branch August 28, 2024 13:42
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.

3 participants