I recently tried to recompile uv 0.2.30 (for testing) which has a dependency on reqwest-middleware and reqwest-retry:
https://github.com/astral-sh/uv/blob/0.2.30/Cargo.lock#L3123
However that specific commit does no longer exist/is dangling: astral-sh/reqwest-middleware@21ceec9
It will be removed from GitHub when the reflog expires (about 90 days IIRC)
Can you please do either of
- avoid removing commits from repositories that are used elsewhere
- tag such commits (e.g. as
reqwests-uv-2.x) to avoid them from expiring
- avoid using commits not in some branch that will not be deleted, such as
main
Otherwise this creates headaches for maintainers of "build scripts", e.g. packages for distros, container images or us at EasyBuild (software build software for HPC)
I recently tried to recompile uv 0.2.30 (for testing) which has a dependency on reqwest-middleware and reqwest-retry:
https://github.com/astral-sh/uv/blob/0.2.30/Cargo.lock#L3123
However that specific commit does no longer exist/is dangling: astral-sh/reqwest-middleware@21ceec9
It will be removed from GitHub when the reflog expires (about 90 days IIRC)
Can you please do either of
reqwests-uv-2.x) to avoid them from expiringmainOtherwise this creates headaches for maintainers of "build scripts", e.g. packages for distros, container images or us at EasyBuild (software build software for HPC)