Skip to content

Reference no update command in uv sync version mismatch#13258

Closed
maxmynter wants to merge 1 commit intoastral-sh:mainfrom
maxmynter:self-update-msg
Closed

Reference no update command in uv sync version mismatch#13258
maxmynter wants to merge 1 commit intoastral-sh:mainfrom
maxmynter:self-update-msg

Conversation

@maxmynter
Copy link
Contributor

Closes: #13253

Summary

(Very) small change to refer to update command uv self update when the uv version is mismatched.

I found only this one occurrence where a reference is suitable. Only other contenders are here

#[error("The lockfile at `uv.lock` uses an unsupported schema version (v{1}, but only v{0} is supported). Downgrade to a compatible uv version, or remove the `uv.lock` prior to running `uv lock` or `uv sync`.")]
UnsupportedLockVersion(u32, u32),
#[error("Failed to parse `uv.lock`, which uses an unsupported schema version (v{1}, but only v{0} is supported). Downgrade to a compatible uv version, or remove the `uv.lock` prior to running `uv lock` or `uv sync`.")]
UnparsableLockVersion(u32, u32, #[source] toml::de::Error),

But I think this would rather convolute the message and they will run into the other message when running uv sync.

Note

Happy to also try my look with implementing your feedback on #11869 if that's ok for you, @aarondobbing?

Test Plan

Local test

@maxmynter
Copy link
Contributor Author

I don't think that the CI failures are related to this change. Locally, I get them on main (041c7a5) too.

@konstin
Copy link
Member

konstin commented May 2, 2025

Fixed the CI error in #13259

@charliermarsh
Copy link
Member

Unfortunately this also got PR'd in #13305, so sorry for the overlap!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Quality of life - suggest uv self update if needed

4 participants