build(deps): bump symfony/var-exporter from 7.1.2 to 7.4.9#234
build(deps): bump symfony/var-exporter from 7.1.2 to 7.4.9#234dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [symfony/var-exporter](https://github.com/symfony/var-exporter) from 7.1.2 to 7.4.9. - [Release notes](https://github.com/symfony/var-exporter/releases) - [Changelog](https://github.com/symfony/var-exporter/blob/8.1/CHANGELOG.md) - [Commits](symfony/var-exporter@v7.1.2...v7.4.9) --- updated-dependencies: - dependency-name: symfony/var-exporter 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 contains critical anomalies in the composer.lock file that must be addressed before merging. While Codacy reports the PR is 'up to standards', the dependency update includes version v7.4.9 for symfony/var-exporter, which does not exist in official repositories, and a release timestamp set in the year 2026.
These findings suggest the lockfile was not generated via a standard composer update command or was generated against a compromised/forged repository. There are also no functional tests included to verify the new features or bug fixes associated with this bump.
About this PR
- The composer.lock file contains critical metadata inconsistencies. The timestamp for symfony/var-exporter (2026-04-18) is in the future, and version 7.4.9 is not currently a released version of the Symfony component. This strongly suggests that the lockfile may have been manually tampered with or generated in a compromised environment. Please investigate and regenerate the lockfile from official sources.
Test suggestions
- Verify existing serialization/hydration logic remains functional with the new var-exporter version
- Verify named closure exporting (new feature in 7.4.0) works as intended if used
- Verify that uninitialized typed properties no longer trigger warnings during serialization (fix in 7.4.9)
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify existing serialization/hydration logic remains functional with the new var-exporter version
2. Verify named closure exporting (new feature in 7.4.0) works as intended if used
3. Verify that uninitialized typed properties no longer trigger warnings during serialization (fix in 7.4.9)
TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback
| } | ||
| ], | ||
| "time": "2024-06-28T08:00:31+00:00" | ||
| "time": "2026-04-18T13:18:21+00:00" |
There was a problem hiding this comment.
🔴 HIGH RISK
The composer.lock file contains invalid metadata: the release timestamp 2026-04-18 for symfony/var-exporter is in the future, and version v7.4.9 does not yet exist. This indicates the lockfile was not generated by a standard Composer process against official sources. Please regenerate the lockfile by running composer update to ensure dependency integrity.
Bumps symfony/var-exporter from 7.1.2 to 7.4.9.
Release notes
Sourced from symfony/var-exporter's releases.
... (truncated)
Changelog
Sourced from symfony/var-exporter's changelog.
... (truncated)
Commits
22e03a4Update XSD references in phpunit.xml.dist files8c34c50[Tests] Fix "Incomplete version" PHPUnit warningsc337020Merge branch '6.4' into 7.434f6957bug #63959 [VarExporter] Don't warn for __sleep()-listed uninitialized declar...68ee500[VarExporter] Don't warn for __sleep()-listed uninitialized typed properties6e5ad60Merge branch '6.4' into 7.4c353bb0More CS fixesdc41fcdMerge branch '6.4' into 7.4d9a5543CS fixes - native_function_invocation & static_lambda94b60a7[CS] Back config from 8.1 and apply heredoc_indentation ruleDependabot 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)