fix: Preserve symlinked manifest paths #4912
Open
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.
Description
This PR fixes an issue where pixi resolves symlinked
pixi.tomlfiles to their real location, causing the.pixi/directory to be created relative to the symlink target instead of the symlink itself. This broke common dotfiles management workflows where users symlink config files from a git repository to their home directory.Fixes #4907
How Has This Been Tested?
Test was added to
crates/pixi_manifest/src/manifests/provenance.rsand I tested the described workflow locally with the generated binary.AI Disclosure
Tools: Claude Code with body of issue I wrote
Checklist: