fix(deps): promote symfony/yaml to a production dependency#3543
Merged
Conversation
symfony/yaml was never declared in composer.json. It was only present in the environment as a transitive dev dependency of codeception/codeception (require-dev), so a production `composer install --no-dev` shipped without it -- while it is used at runtime in: - app/Domain/Blueprints/Services/TemplateRegistry.php (Yaml::parseFile on every blueprint/canvas template load) - app/Core/Configuration/Environment.php (YAML config file in the boot config priority chain) Production therefore threw `Class "Symfony\Component\Yaml\Yaml" not found` as soon as a canvas was opened. Add it to `require` (^7.2, matching the other symfony 7 components) and regenerate the lock so it moves into the production packages array. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
marcelfolaron
requested review from
broskees and
Copilot
and removed request for
a team
Contributor
There was a problem hiding this comment.
Pull request overview
Promotes symfony/yaml from a transitive dev-only dependency to an explicit production dependency so runtime YAML parsing (Symfony\Component\Yaml\Yaml) is available in --no-dev installs.
Changes:
- Add
symfony/yaml: ^7.2tocomposer.jsonproductionrequire. - Regenerate
composer.lockto movesymfony/yamlfrompackages-devinto productionpackages(resolved tov7.4.13).
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| composer.json | Declares symfony/yaml as a direct production dependency. |
| composer.lock | Reflects the dependency promotion by relocating symfony/yaml into production packages and updating the content hash. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Jun 18, 2026
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
symfony/yamlwas never declared incomposer.json— neither inrequirenorrequire-dev. It only existed in the environment as a transitive dev dependency ofcodeception/codeception(arequire-devpackage).composer why symfony/yamlonmastershows only Codeception requires it; everything else (symfony/routing,symfony/translation,roave/security-advisories) merely conflicts with old versions, which installs nothing. Incomposer.lockthe package sat in thepackages-devarray.The result: a production
composer install --no-devships withoutsymfony/yaml, yet it is used at runtime in:app/Domain/Blueprints/Services/TemplateRegistry.php—Yaml::parseFile()on every blueprint/canvas template loadapp/Core/Configuration/Environment.php— YAML config file in the boot config priority chainSo production throws
Class "Symfony\Component\Yaml\Yaml" not foundthe moment a canvas is opened (and potentially at boot if a YAML config is present).Fix
"symfony/yaml": "^7.2"torequire(matching the other symfony 7 components, e.g.symfony/cache: ^7.2).composer.lockso the package (resolved atv7.4.13) moves frompackages-devinto the productionpackagesarray.No code changes needed — the usages were correct, only the dependency declaration was missing.
Verification
composer why symfony/yamlnow listsleantime/leantime ... requires symfony/yaml (^7.2)as a direct requirer.composer.lock, thesymfony/yamlentry is now before thepackages-devboundary (productionpackages).composer install --no-dev --dry-runno longer listssymfony/yamlfor removal — it stays installed.🤖 Generated with Claude Code