late-queen-51746
07/03/2026, 3:50 PMmodern-fireman-99755
07/03/2026, 3:55 PMmodern-fireman-99755
07/03/2026, 3:55 PMlate-queen-51746
07/03/2026, 4:04 PMmodern-fireman-99755
07/03/2026, 5:15 PMmodern-fireman-99755
07/03/2026, 5:16 PMlate-queen-51746
07/04/2026, 4:08 AMmodern-fireman-99755
07/04/2026, 10:09 AMnutritious-balloon-65098
07/04/2026, 10:10 AMnutritious-balloon-65098
07/04/2026, 11:01 AMuv should be able to resolve 1.31.0 from PyPI.
If someone is “stuck” on 1.14.0, likely causes are local/project constraints rather than PyPI lag, e.g.:
• pinned versions in pyproject.toml
• an existing uv.lock that pins 1.14.0
• using uv sync --frozen
• uv exclude-newer / a date cutoff
• using a corporate PyPI mirror that syncs slowly
Given the above, I would not open an issue claiming PyPI/uv are behind GitHub releases, because the data doesn’t support it.
If you want, paste the relevant parts of your pyproject.toml + uv.lock (or tell me if you’re using exclude-newer / a mirror), and I can point to the exact reason you’re not picking up 1.31.0.modern-fireman-99755
07/04/2026, 11:02 AM