chore(deps): bump hf-hub from 0.5.0 to 1.0.0

[dependabot]

Bumps hf-hub from 0.5.0 to 1.0.0.

Changelog

Sourced from hf-hub's changelog.

Releasing hf-hub

This document covers the full release process for the hf-hub crate. If anything here is unclear or out of date, please open a PR.

What gets released

A single tag push releases one artifact:

• hf-hub Rust crate on crates.io, via .github/workflows/rust-release.yml.

The workflow triggers on tags matching v* (e.g., v1.0.0, v1.0.0-rc.0).

There are no Python components in this repo. The other workspace members are not published:

• hfrs/ — CLI binary, distributed via cargo install --git.
• examples/, benches/, integration-tests/ — internal-only, version 0.0.0, never published.

Pre-release checklist

1. CI is green on main. The Rust workflow must be passing on every platform in the matrix (Ubuntu, Windows, macOS) with both feature configurations ("" and --all-features).
2. Review the diff since the last release.

   git log --oneline v0.5.0..main
   git diff v0.5.0..main --stat -- hf-hub/

   Pay particular attention to changes under hf-hub/src/ — those are the only changes that actually ship to crates.io.
3. Identify breaking changes. Anything that changes the public Rust API (types, function signatures, removed re-exports, builder fields) needs to be reflected in the version bump per semver and called out in the release notes.
4. Run the full pre-release test sweep (see next section).

Pre-release test sweep

Run all of these from the repo root before tagging. They mirror what CI runs, plus a publish dry-run that CI does not currently do.

Format and lint

cargo +nightly fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo clippy --workspace --all-targets --all-features -- -D warnings

Unit tests (hf-hub)

cargo test -p hf-hub
cargo test -p hf-hub --features blocking

Integration tests (integration-tests)

... (truncated)

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)