Skip to content

Update some details about uv - #28

Open
alakae wants to merge 1 commit into
mprpic:mainfrom
alakae:uv
Open

Update some details about uv#28
alakae wants to merge 1 commit into
mprpic:mainfrom
alakae:uv

Conversation

@alakae

@alakae alakae commented Aug 7, 2026

Copy link
Copy Markdown

Updated documentation for exclude-newer-package settings and usage, including timestamp format and CLI options.

Updated documentation for `exclude-newer-package` settings and usage, including timestamp format and CLI options.
Comment thread README.md
**This cutoff is an absolute timestamp, not a rolling window — it does not advance with time.** Left in place, it
doesn't expire; it permanently pins the package to whatever was newest as of that date and blocks every later
release forever. So it still needs to be removed once the general cooldown has caught up to it — it just fails
differently than `false` if forgotten: it freezes updates instead of permanently exempting them.

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure that this is better than a temporary disable using a CLI option (using false) and an exact version specifier (e.g. ==1.2.3). If someone forgets the timestamp in their uv.toml file, they will end up with an outdated version very soon. The use case for marking packages as false in the config file is purely for things that can be trusted (for example my own packages that I publish and install right away).

Maybe we just want to make it more explicit in the docs that using pkg=false in the config file carries dangers (though it feels obvious to state that)?

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.

2 participants