Conversation
Member
Author
|
Dépends on how you look at it. As we test unreleased Symfony versions, the CI fails for something we do not support yet. By supporting this change; this fix the CI fails. No bug happen to anyone now, but will when/if people migrate to AssetMapper new bundle in 8.2 |
Member
Kocal
reviewed
Sep 13, 2026
|
|
||
| ## 3.5.0 | ||
|
|
||
| - Fix AssetMapper detection with Symfony 8.2's standalone `AssetMapperBundle` |
Member
There was a problem hiding this comment.
I would go for:
Suggested change
| - Fix AssetMapper detection with Symfony 8.2's standalone `AssetMapperBundle` | |
| - Add support for AssetMapper 8.2+ |
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.

Add support for the AssetMapper 8.2 new bundle (fix CI failures with 8.2 in the same time)