61 Commits

Author	SHA1	Message	Date
konsti	494a1d782d	Publish: Workaround using raw filename (#8204)	2024-10-15 14:22:52 +02:00
samypr100	01c44af3c3	chore: unify all env vars used (#8151) ... ## Summary This PR declares and documents all environment variables that are used in one way or another in `uv`, either internally, or externally, or transitively under a common struct. I think over time as uv has grown there's been many environment variables introduced. Its harder to know which ones exists, which ones are missing, what they're used for, or where are they used across the code. The docs only documents a handful of them, for others you'd have to dive into the code and inspect across crates to know which crates they're used on or where they're relevant. This PR is a starting attempt to unify them, make it easier to discover which ones we have, and maybe unlock future posibilities in automating generating documentation for them. I think we can split out into multiple structs later to better organize, but given the high influx of PR's and possibly new environment variables introduced/re-used, it would be hard to try to organize them all now into their proper namespaced struct while this is all happening given merge conflicts and/or keeping up to date. I don't think this has any impact on performance as they all should still be inlined, although it may affect local build times on changes to the environment vars as more crates would likely need a rebuild. Lastly, some of them are declared but not used in the code, for example those in `build.rs`. I left them declared because I still think it's useful to at least have a reference. Did I miss any? Are their initial docs cohesive? Note, `uv-static` is a terrible name for a new crate, thoughts? Others considered `uv-vars`, `uv-consts`. ## Test Plan Existing tests	2024-10-14 16:48:13 -05:00
Amos Wenger	715f28fd39	chore: Move all integration tests to a single binary (#8093) ... As per https://matklad.github.io/2021/02/27/delete-cargo-integration-tests.html Before that, there were 91 separate integration tests binary. (As discussed on Discord — I've done the `uv` crate, there's still a few more commits coming before this is mergeable, and I want to see how it performs in CI and locally).	2024-10-11 16:41:35 +02:00
konsti	282fab5f70	Hint at wrong endpoint in publish (#7872) ... Improve hints when using the simple index URL instead of the upload URL in `uv publish`. This is the most common confusion when publishing, so we give it some extra care and put it more centrally in the CLI help. Fixes #7860 --------- Co-authored-by: Zanie Blue <contact@zanie.dev>	2024-10-08 19:16:02 +00:00
konsti	fc495876cf	Clear publish progress bar on retry (#7921)	2024-10-04 13:15:26 +02:00
Charlie Marsh	14507a1793	Add `uv-` prefix to all internal crates (#7853) ... ## Summary Brings more consistency to the repo and ensures that all crates automatically show up in `--verbose` logging.	2024-10-01 20:15:32 -04:00
konsti	8177974439	Follow-up: Add gitignore to dist directory (#7840)	2024-10-01 15:38:37 +02:00
konsti	16a6fd2c42	Add retries to `uv publish` (#7635)	2024-09-24 16:24:44 +00:00
konsti	205bf8cabe	Implement trusted publishing (#7548) ... Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2024-09-24 16:07:20 +00:00
konsti	c053dc84f4	Progress bars for `uv publish` (#7613)	2024-09-24 15:55:33 +00:00
konsti	1995d20298	Add `uv publish`: Basic upload with username/password or keyring (#7475) ... Co-authored-by: Charlie Marsh <charlie.r.marsh@gmail.com>	2024-09-24 15:33:06 +00:00