Conversation
No test since we don't know where the test runner will have access to `/` or not. I've manually confirmed that `uv init / --name foo` doesn't panic anymore. The error message for it is mediocre but passable (same as e.g. `uv init /usr` on stable, no change just documenting it): ``` error: Failed to initialize Git repository at `/` stdout: stderr: /.git: Permission denied ```
konstin
commented
Feb 12, 2026
| Some(parent) => parent, | ||
| None => { | ||
| if path.is_dir() { | ||
| // Support creating a project in the filesystem root (`/` on Unix). |
Member
Author
There was a problem hiding this comment.
Less because we encourage it, and more because I expect there some strange environment where a filesystem root is a reasonable directory.
EliteTK
approved these changes
Feb 15, 2026
tmeijn
pushed a commit
to tmeijn/dotfiles
that referenced
this pull request
Feb 18, 2026
This MR contains the following updates: | Package | Update | Change | |---|---|---| | [uv](https://github.com/astral-sh/uv) | patch | `0.10.3` → `0.10.4` | MR created with the help of [el-capitano/tools/renovate-bot](https://gitlab.com/el-capitano/tools/renovate-bot). **Proposed changes to behavior should be submitted there as MRs.** --- ### Release Notes <details> <summary>astral-sh/uv (uv)</summary> ### [`v0.10.4`](https://github.com/astral-sh/uv/blob/HEAD/CHANGELOG.md#0104) [Compare Source](astral-sh/uv@0.10.3...0.10.4) Released on 2026-02-17. ##### Enhancements - Remove duplicate references to the affected paths when showing `uv python` errors ([#​18008](astral-sh/uv#18008)) - Skip discovery of workspace members that contain only git-ignored files, including in sub-directories ([#​18051](astral-sh/uv#18051)) ##### Bug fixes - Don't panic when initialising a package at the filesystem root (e.g. `uv init / --name foo`) ([#​17983](astral-sh/uv#17983)) - Fix permissions on `wheel` and `sdist` files produced by the `uv_build` build backend ([#​18020](astral-sh/uv#18020)) - Revert locked file change to fix locked files on NFS mounts ([#​18071](astral-sh/uv#18071)) </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this MR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this MR, check this box --- This MR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0My4xOS4yIiwidXBkYXRlZEluVmVyIjoiNDMuMTkuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiUmVub3ZhdGUgQm90IiwiYXV0b21hdGlvbjpib3QtYXV0aG9yZWQiLCJkZXBlbmRlbmN5LXR5cGU6OnBhdGNoIl19-->
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
2 participants
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.
No test since we don't know where the test runner will have access to
/or not. I've manually confirmed thatuv init / --name foodoesn't panic anymore.The error message for it is mediocre but passable (same as e.g.
uv init /usron stable, no change just documenting it):