Sourced from hf-hub's releases.
v0.5.0
What's Changed
- Upgrade ureq by
@Narsilin huggingface/hf-hub#114- Update indicatif to current version in Cargo.toml by
@gordonmessmerin huggingface/hf-hub#126- Fix failing API tests due to outdated model metadata expectations by
@bmqubein huggingface/hf-hub#124- fix: fix typo by
@AndyDai-nvin huggingface/hf-hub#121- Updating tests and dependencies. by
@Narsilin huggingface/hf-hub#127- Remove markdown from Cargo.toml by
@gordonmessmerin huggingface/hf-hub#128- Fixup the docstrings for download function (which always downloads). by
@Narsilin huggingface/hf-hub#130- Expose
metadataandpointer_pathmethods by@danieldkin huggingface/hf-hub#136New Contributors
@gordonmessmermade their first contribution in huggingface/hf-hub#126@bmqubemade their first contribution in huggingface/hf-hub#124@AndyDai-nvmade their first contribution in huggingface/hf-hub#121@danieldkmade their first contribution in huggingface/hf-hub#136Full Changelog: https://github.com/huggingface/hf-hub/compare/v0.4.3...v0.5.0
Sourced from hf-hub's changelog.
Releasing hf-hub
This document covers the full release process for the
hf-hubcrate. If anything here is unclear or out of date, please open a PR.What gets released
A single tag push releases one artifact:
hf-hubRust 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 viacargo install --git.examples/,benches/,integration-tests/— internal-only, version0.0.0, never published.Pre-release checklist
- CI is green on
main. TheRustworkflow must be passing on every platform in the matrix (Ubuntu, Windows, macOS) with both feature configurations (""and--all-features).- Review the diff since the last release.
Pay particular attention to changes undergit log --oneline v0.5.0..main git diff v0.5.0..main --stat -- hf-hub/hf-hub/src/— those are the only changes that actually ship to crates.io.- 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.
- 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 warningsUnit tests (
hf-hub)cargo test -p hf-hub cargo test -p hf-hub --features blockingIntegration tests (
integration-tests)
... (truncated)
b86d34c
release: 0.5.05510260
Expose metadata and pointer_path methods (#136)94b8385
Fixup the docstrings for download function (which always downloads). (#130)c165283
Remove markdown from Cargo.toml (#128)2c1f231
Updating tests and dependencies. (#127)6fcb56d
fix typo (#121)1d3037a
Fix failing API tests due to outdated model metadata expectations (#124)65fb034
Update indicatif to current version in Cargo.toml (#126)3c9391b
Upgrade ureq (#114)