build(deps): bump symfony/filesystem from 7.1.2 to 7.4.9#236
build(deps): bump symfony/filesystem from 7.1.2 to 7.4.9#236dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [symfony/filesystem](https://github.com/symfony/filesystem) from 7.1.2 to 7.4.9. - [Release notes](https://github.com/symfony/filesystem/releases) - [Changelog](https://github.com/symfony/filesystem/blob/8.1/CHANGELOG.md) - [Commits](symfony/filesystem@v7.1.2...v7.4.9) --- updated-dependencies: - dependency-name: symfony/filesystem dependency-version: 7.4.9 dependency-type: indirect update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 0 |
AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.
TIP This summary will be updated as you push new changes.
There was a problem hiding this comment.
Pull Request Overview
This PR updates symfony/filesystem and its associated polyfills. Although the Codacy analysis is up to standards with no new issues, the update introduces potential breaking changes for the infrastructure.
Specifically, the symfony/polyfill-mbstring update requires the ext-iconv PHP extension, which may be missing in minimalist runtime environments. Additionally, the lock file was generated with a significantly newer version of Composer (2.9.0), which could cause compatibility issues with CI/CD pipelines running older versions. These architectural concerns should be validated before merging.
About this PR
- The
composer.lockfile was updated using a newer Composer version (plugin-api-version 2.9.0 vs 2.6.0). This may cause installation errors in CI environments or production servers that use older Composer binaries. It is recommended to synchronize the Composer version used locally with the one used in the deployment pipeline.
Test suggestions
- Verify application compatibility with symfony/filesystem v7.4.9, particularly regarding Path normalization changes mentioned in release notes.
- Confirm that the runtime environment includes 'ext-iconv', which is now an explicit requirement for symfony/polyfill-mbstring v1.37.0.
- Ensure the PHP version in the target environment satisfies the new >= 7.2 requirement for polyfill packages (though likely satisfied if using Symfony 7).
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify application compatibility with symfony/filesystem v7.4.9, particularly regarding Path normalization changes mentioned in release notes.
2. Confirm that the runtime environment includes 'ext-iconv', which is now an explicit requirement for symfony/polyfill-mbstring v1.37.0.
3. Ensure the PHP version in the target environment satisfies the new >= 7.2 requirement for polyfill packages (though likely satisfied if using Symfony 7).
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| }, | ||
| "require": { | ||
| "php": ">=7.1" | ||
| "ext-iconv": "*", |
There was a problem hiding this comment.
🔴 HIGH RISK
The update to symfony/polyfill-mbstring v1.37.0 introduces a mandatory requirement for the ext-iconv PHP extension. This will cause installation or runtime failures in environments where the iconv extension is not explicitly installed (e.g., minimalist Docker images). Please verify that all target environments have ext-iconv enabled.
Bumps symfony/filesystem from 7.1.2 to 7.4.9.
Release notes
Sourced from symfony/filesystem's releases.
... (truncated)
Commits
dcd8f96Update XSD references in phpunit.xml.dist filesd230a8eMerge branch '6.4' into 7.429f792dMore CS fixese66da3eMerge branch '6.4' into 7.460d2511CS fixes - native_function_invocation & static_lambda1c54ad0[Filesystem] Fix Path dealing with schemesb42ef66[Filesystem] Fix merge conflict resolutionb6c73d5Merge branch '6.4' into 7.47309213[Filesystem] Fix Path::normalize() replacing backslashes on UNIX5dce1cdAdd deprecationTrigger ignoreUndefinedTriggers="true" in phpunit.xml.dist filesDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)