You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since 2026-08-27 the Nix workflow fails in "Build the package": every crate tarball fetch from https://crates.io/api/v1/crates/<name>/<version>/download returns HTTP 403 (cannot download crate-<name>.tar.gz from any mirror), for pre-existing crates too. The last green run was 2026-08-19 on main with the same flake.lock pin (nixpkgs 8c809a14, 2026-03-03), so the change is on the crates.io side. That API endpoint is deprecated for non-cargo clients; newer nixpkgs importCargoLock fetches from static.crates.io.
Watch the Flake check: it fails on the first crate download, and a rerun fails the same way.
Expected behavior
The flake builds.
Screenshots
None.
Desktop (please complete the following information):
OS: CI, ubuntu-latest
Terminal: n/a
Version: main
Additional context
The fix is nix flake update nixpkgs (a flake.lock bump). The check is not in the main ruleset, so it does not block merges, but it is red on every PR that touches the lock until then.
Describe the bug
Since 2026-08-27 the Nix workflow fails in "Build the package": every crate tarball fetch from
https://crates.io/api/v1/crates/<name>/<version>/downloadreturns HTTP 403 (cannot download crate-<name>.tar.gz from any mirror), for pre-existing crates too. The last green run was 2026-08-19 onmainwith the sameflake.lockpin (nixpkgs8c809a14, 2026-03-03), so the change is on the crates.io side. That API endpoint is deprecated for non-cargo clients; newer nixpkgsimportCargoLockfetches fromstatic.crates.io.To Reproduce
Cargo.lock(for example feat(sources): add Qobuz #489).Flakecheck: it fails on the first crate download, and a rerun fails the same way.Expected behavior
The flake builds.
Screenshots
None.
Desktop (please complete the following information):
Additional context
The fix is
nix flake update nixpkgs(aflake.lockbump). The check is not in themainruleset, so it does not block merges, but it is red on every PR that touches the lock until then.