feat: add resolve-symlinks option to control symlink behavior in manifest paths
#5171
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
Adds a
resolve-symlinksoption to the[workspace]section that controlshow pixi handles symlinked manifest files.
By default (
true), pixi fully resolves symlinks to determine the workspace root from the real file location.This restores the original behavior that was changed in #4912 and #5059, fixing the regression reported in #5148.
How Has This Been Tested?
I built the binary locally and tested both workflows by setting the new
resolve-symlinksflag.AI Disclosure
Tools: Claude Opus 4.5
Checklist:
schema/model.py.