Skip to content

Don't remove still-referenced files when unconfiguring recipes#1054

Merged
nicolas-grekas merged 1 commit into2.xfrom
fix-unconfig
May 28, 2025
Merged

Don't remove still-referenced files when unconfiguring recipes#1054
nicolas-grekas merged 1 commit into2.xfrom
fix-unconfig

Conversation

@nicolas-grekas
Copy link
Copy Markdown
Member

Instead of #706
Fixes broken logic added in #451, which didn't account for folders.
The new logic uses only the symfony.lock file and not the recipe anymore to decide which files to remove.

@nicolas-grekas nicolas-grekas merged commit 4ae50d3 into 2.x May 28, 2025
6 of 7 checks passed
@nicolas-grekas nicolas-grekas deleted the fix-unconfig branch May 28, 2025 14:23
fabpot added a commit that referenced this pull request Aug 22, 2025
…wouterj)

This PR was merged into the 2.x branch.

Discussion
----------

Don't remove still-referenced files when updating recipes

A twin to #1054

When a recipe removes a file in a newer recipe version, we should also check if other recipes still reference that file.

Real use-case: This occurs when you need to keep the PhpunitBridge in 7.3 (e.g. you need the clock mock).

Commits
-------

03ac318 Don't remove still-referenced files when updating recipes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant