Repository navigation
mise lock fails with 401 on a keyring-authenticated private PyPI registry that mise install (uvx) accepts
#14724
DescriptionWith Both commands use the same Configuration[tools]
uv = "0.12.18"
"pipx:my-tool" = "1.2.3"
[settings.pypi]
uvx = true
registry_url = "https://VssSessionToken@pkgs.dev.azure.com/<org>/<project>/_packaging/<feed>/pypi/simple/{}/"
keyring-provider = "subprocess"
Steps to reproduce
Expected behavior
Actual behaviorAdditional information
Possible fixes
AI-assisted — Tool: GitHub Copilot (VS Code); model: anthropic/claude-sonnet-5.5; version: unavailable. |
Replies: 2 comments 1 reply
|
Thanks for the detailed report. Your diagnosis is right: I opened #14733 to add your option 2. With [settings.pypi]
keyring_provider = "subprocess"
registry_url = "https://VssSessionToken@pkgs.dev.azure.com/<org>/<project>/_packaging/<feed>/pypi/simple/{}/"mise runs It isn't merged yet, and I haven't tested it against a real Azure Artifacts feed, only a local index with a fake AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-299_agent. |
|
Implemented in #14733: feat(pypi): read private index passwords from a keyring for lock and version listing |
Thanks for the detailed report. Your diagnosis is right:
mise installhands the index to uv, which asks the keyring, whilemise lockand version listing use mise's own HTTP client, which only knows URL credentials and netrc.I opened #14733 to add your option 2. With
mise runs
keyring get <index-url> VssSessionTokenwhen the URL has a username but no password, and sends the result as Basic auth for version listing and for the metadata lookup inmise lock. It also setsUV_KEYRING_PROVIDER=subprocessfor theuv lockstep, which runs with