Skip to content

build(deps-dev): bump the dependencies group across 1 directory with 3 updates - #1677

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/requirement-checker/dependencies-5a73183ef8
Open

build(deps-dev): bump the dependencies group across 1 directory with 3 updates#1677
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/composer/requirement-checker/dependencies-5a73183ef8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 2, 2026

Copy link
Copy Markdown
Contributor

Bumps the dependencies group with 3 updates in the /requirement-checker directory: fidry/makefile, phpunit/phpunit and symfony/yaml.

Updates fidry/makefile from 1.0.3 to 1.1.2

Release notes

Sourced from fidry/makefile's releases.

1.1.2

Fixes

  • Add missing dependency on mbstring (#76)

1.1.1

Features

  • Remove remaining occurrences of Safe* code (#66)

1.1.0

Features

  • Bump min PHP version supported to PHP 8.3 (#63)
Commits
  • 8466e99 build: Add missing dependency on mbstring (#76)
  • 7657cc5 build(deps-dev): Bump the dependencies group in /vendor-bin/php-cs-fixer with...
  • 9bee9fe build(deps-dev): Update infection/infection requirement from ^0.29 to ^0.32 i...
  • 28e9c1a build(deps): Bump the dependencies group (#74)
  • c70487b build(deps-dev): Bump rector/rector (#72)
  • 7a1ba59 build: Configure all tmp artefacts to go to var (#71)
  • 77cef76 ci: Update dependabot (#70)
  • 21392f0 chore: Update Psalm (#69)
  • 0852adf ci: Add PHP 8.5 (#68)
  • 1b11698 ci: Pin dependencies (#67)
  • Additional commits viewable in compare view

Updates phpunit/phpunit from 10.5.66 to 13.4.5

Release notes

Sourced from phpunit/phpunit's releases.

PHPUnit 13.4.5

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

Learn how to install or update PHPUnit 13.4 in the documentation.

Keep up to date with PHPUnit:

PHPUnit 13.4.4

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

Learn how to install or update PHPUnit 13.4 in the documentation.

Keep up to date with PHPUnit:

PHPUnit 13.4.3

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence

... (truncated)

Changelog

Sourced from phpunit/phpunit's changelog.

[13.4.5] - 2026-10-27

Fixed

  • The static analysis cache directory that is automatically created in the operating system's path used for temporary files when no cache directory is configured is not used when the POSIX extension is not loaded

[13.4.4] - 2026-10-27

Fixed

  • The TeamCity logger writes testSuiteFinished twice for a test class when one of its before-first-test methods errors or fails
  • The TestDox output shows a less important outcome of a test that has more than one outcome, for instance the failure in tearDown() of a test that errored
  • When the test run is interrupted by a signal while a test is run in process isolation, the result of the test is discarded and the test is counted as passed, and the TestDox output cannot be printed
  • When no static analysis cache directory is configured, the cache directory that is automatically created in the operating system's path used for temporary files is also used when it was created by another user or can be written to by other users
  • The directory in the operating system's path used for temporary files in which the temporary files for collecting code coverage for a PHPT test are created has a fixed name, and is also used when it was created by another user, who can then replace the code of the PHPT test before it is executed

[13.4.3] - 2026-10-16

Fixed

  • The dependencies of a test that are listed after a dependency on a test that does not return a value, or after a dependency on a larger test, were not checked, so the test was run instead of being skipped when one of these dependencies had not passed
  • Tests could not be run in process isolation when the namespace of the test class begins with a name that the code of the child process imports, for instance CodeCoverage or Facade
  • A test that is run in process isolation aborts the test run when its data set or a value returned by a test it depends on cannot be serialized, for instance because it is a closure
  • When a before-first-test method or an after-last-test method errors or fails, the remaining methods of the same kind are still called, and each of them that does not error or fail itself is reported with the exception of the earlier method
  • When a hook method of a test, for instance a #[Before] method, skips the test, the remaining hook methods of the same kind are still called, so the test is reported as errored instead of skipped when one of them errors
  • An error or failure in a before-first-test method or an after-last-test method that is called again in the child process of a test that is run in process isolation is reported twice, once for the test class and once for the test
  • When a before-first-test method errors, the progress output shows one E for the test class instead of one for each of its tests, only one of its tests is counted as run, and the test that is run next is shown as an error
  • When a before-first-test method fails, the progress output shows nothing for the tests of the test class and only one of them is counted as run
  • The Open Test Reporting XML logfile has no start for a test that errors before it is prepared, for instance because it depends on a test that does not exist, and no end for the test that is run after a test that is skipped because a test it depends on did not pass or because one of its requirements is not met
  • The Open Test Reporting XML logfile has no entry for a test that is marked as incomplete before it is prepared, for instance in setUp(), and reports the test that is run after it as aborted with the message of the incomplete test
  • The Open Test Reporting XML logfile has no end for the test that is run after a test whose preparation errors, for instance because setUp() raises an exception or the global state cannot be backed up
  • The Open Test Reporting XML logfile reports a test that has more than one outcome, for instance because tearDown() fails after the test errored, with its last outcome instead of its most severe one, and with more than one end when the preparation of the test errored
  • The Open Test Reporting XML logfile is not well-formed when a test name, a message, the output of a test, or the string representation of an exception contains ]]>, bytes that are not valid UTF-8, or characters that are not allowed in XML, for instance the escape character of an ANSI escape sequence
  • The Open Test Reporting XML logfile reports an issue that is triggered before a test is prepared, for instance in setUp(), with an empty ID before the start of the test

[13.4.2] - 2026-10-12

Fixed

  • #7033: Compact printer is created although an extension replaces the progress output
  • #7035: Sorting tests by duration recomputes the duration of a test suite for every comparison
  • Sorting tests by size recomputes the size of a test suite for every comparison
  • expectUserDeprecationMessage() and expectUserDeprecationMessageMatches() did not see the deprecations triggered by an attempt of a retried test and saw those of the previously run test instead
  • The status of a test whose mock object raises an exception in its destructor is success although the test is reported as errored, so #[Retry] does not retry the test, --repeat does not skip the remaining repetitions, tearDown() sees the wrong status, and code coverage records the test as successful
  • Named arguments passed to with() were matched by position instead of by name, so an expectation such as ->with(b: 7) compared the expected value with the first parameter of the method and the parameter named $b was not checked
  • String keys of the parameter sets passed to withParameterSetsInOrder(), withParameterSetsInAnyOrder(), and withParameterSetsInPartialOrder() were ignored, so a parameter set such as ['b' => 7] compared the expected value with the first parameter of the method and the parameter named $b was not checked

... (truncated)

Commits
  • 941457a Prepare release
  • 2080b37 Merge branch '12.5' into 13.4
  • 1d6dbe7 Prepare release
  • ef98204 Merge branch '12.5' into 13.4
  • 15fb431 Do not require the POSIX extension for using the automatically created static...
  • 71b681a Prepare release
  • c056074 Merge branch '12.5' into 13.4
  • 191b2e0 Prepare release
  • ae31c78 Create the temporary files for collecting code coverage for a PHPT test in a ...
  • c4c4f06 Merge branch '12.5' into 13.4
  • Additional commits viewable in compare view

Updates symfony/yaml from 6.4.49 to 8.1.10

Release notes

Sourced from symfony/yaml's releases.

v8.1.10

Changelog (symfony/yaml@v8.1.9...v8.1.10)

[SECURITY] Security release

v8.1.9

Changelog (symfony/yaml@v8.1.8...v8.1.9)

v8.1.8

Changelog (symfony/yaml@v8.1.6...v8.1.8)

v8.1.6

Changelog (symfony/yaml@v8.1.5...v8.1.6)

v8.1.5

Changelog (symfony/yaml@v8.1.2...v8.1.5)

v8.1.2

Changelog (symfony/yaml@v8.1.1...v8.1.2)

... (truncated)

Changelog

Sourced from symfony/yaml's changelog.

CHANGELOG

8.2

  • Add support for the !!null, !!bool and !!int tags, and accept quoted values for them and for !!float
  • Throw a ParseException when the value of a !!float tag is not a valid float, instead of casting it to 0.0
  • Add a gitlab output format to the lint:yaml command
  • Add the Schema namespace with SchemaValidatorInterface, SchemaResolverInterface and their SchemaValidator and FileHeaderSchemaResolver implementations, to validate data against a JSON Schema
  • Add JSON Schema validation to the lint:yaml command when opis/json-schema is installed, with the --check-schema/--no-check-schema and --schema options and the # yaml-language-server: $schema= / # $schema= file headers
  • Add support for parsing a block scalar, optionally tagged, as the root node of a document
  • Require the PARSE_CUSTOM_TAGS flag for custom tags on block scalars, as on other values
  • Resolve built-in tags on block scalars as on inline scalars, and throw on the ones that are not implemented

8.0

  • Remove support for parsing duplicate mapping keys whose value is null

7.3

  • Add compact nested mapping support by using the Yaml::DUMP_COMPACT_NESTED_MAPPING flag
  • Add the Yaml::DUMP_FORCE_DOUBLE_QUOTES_ON_VALUES flag to enforce double quotes around string values

7.2

  • Deprecate parsing duplicate mapping keys whose value is null
  • Add support for dumping null as an empty value by using the Yaml::DUMP_NULL_AS_EMPTY flag

7.1

  • Add support for getting all the enum cases with !php/enum Foo

7.0

  • Remove the !php/const: tag, use !php/const instead (without the colon)

6.3

  • Add support to dump int keys as strings by using the Yaml::DUMP_NUMERIC_KEY_AS_STRING flag

6.2

... (truncated)

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
build(deps-dev): bump the dependencies group across 1 directory with …
52b1501 
…3 updates

Bumps the dependencies group with 3 updates in the /requirement-checker directory: [fidry/makefile](https://github.com/theofidry/makefile), [phpunit/phpunit](https://github.com/sebastianbergmann/phpunit) and [symfony/yaml](https://github.com/symfony/yaml).


Updates `fidry/makefile` from 1.0.3 to 1.1.2
- [Release notes](https://github.com/theofidry/makefile/releases)
- [Commits](theofidry/makefile@1.0.3...1.1.2)

Updates `phpunit/phpunit` from 10.5.66 to 13.4.5
- [Release notes](https://github.com/sebastianbergmann/phpunit/releases)
- [Changelog](https://github.com/sebastianbergmann/phpunit/blob/13.4.5/ChangeLog-13.4.md)
- [Commits](sebastianbergmann/phpunit@10.5.66...13.4.5)

Updates `symfony/yaml` from 6.4.49 to 8.1.10
- [Release notes](https://github.com/symfony/yaml/releases)
- [Changelog](https://github.com/symfony/yaml/blob/8.2/CHANGELOG.md)
- [Commits](symfony/yaml@v6.4.49...v8.1.10)

---
updated-dependencies:
- dependency-name: fidry/makefile
  dependency-version: 1.1.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: phpunit/phpunit
  dependency-version: 13.4.5
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dependencies
- dependency-name: symfony/yaml
  dependency-version: 8.1.10
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Nov 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file php Pull requests that update Php code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants