feat(uv): add SHA256 hashes for uv 0.11.21 and 0.11.7

[daoanhkhoa123]

Add SHA256 mappings for uv releases 0.11.21 and 0.11.7

The hashes were directly from the sha256.sum files published in the uv GitHub releases:

• https://github.com/astral-sh/uv/releases/tag/0.11.21
• https://github.com/astral-sh/uv/releases/tag/0.11.7

No changes aside from this version file for uv.

---

Changes are visible to end-users: no

• Searched for relevant documentation and updated as needed: no
• Breaking change (forces users to change their own code or config): no
• Suggested release notes appear below: no

Test plan

• Covered by existing test cases

• Manual testing:

  • Confirmed that the following setup works correctly:

    bazel_dep(name = "aspect_rules_py", version = "2.0.0-alpha.1")
    
    # For support of uv 0.11.21
    git_override(
        module_name = "aspect_rules_py",
        remote = "https://github.com/daoanhkhoa123/rules_py.git",
        commit = "ce3630ab9c79674ce9fd6f63e69188f97a5ecf36"
    ) 
    
    uv_bin = use_extension("@aspect_rules_py//uv:extensions.bzl", "uv_bin")
    uv_bin.toolchain(version = "0.11.21")
    use_repo(uv_bin, "uv")
    
    uv = use_extension("@aspect_rules_py//uv:extensions.bzl", "uv")
    uv.declare_hub(
        hub_name = "pypi"
    )
    uv.project(
        hub_name = "pypi",
        pyproject = "//:pyproject.toml",
        lock = "//:uv.lock",
    )
    use_repo(uv, "pypi")
    
    register_toolchains("@uv//:all")

  • Expected output:

    $ bazel run @uv -- --version
    uv 0.11.21 (x86_64-unknown-linux-musl)

[CLAassistant]

All committers have signed the CLA.

[xangcastle]

Thanks for using our HEAD version, please follow this example to use any UV release, even custom forks

[daoanhkhoa123]

May i know the reason why you closed the commits? Since i thought it would be a lot cleaner to add uv versions and shorten the bazel code.

[jbedard]

@daoanhkhoa123 I think we want to think about this a bit. Ideally this will be automated, but I think we also don't want to list every version in the world and only list a subset of them.

IMO rules_py should ship with the hashes for the "latest patch of each minor release". Then if you want a different version either:

• you hardcode the hashes yourself
• you hardcode no hashes, they are computed the first time and put into the MODULE.bazel.lock for next time (you must checkin the lockfile so we know the hashes next time)