Repository navigation
fix(ci): bump db-dump so the crates index accepts tar_sha256 - #321
Merged
Merged
Conversation
crates.io versions.csv replaced checksum with tar_sha256, and db-dump 0.7.x rejects that column. 0.10.0 parses the current dump; the loader call sites are unchanged. Co-authored-by: Folyd <Folyd@users.noreply.github.com>
Deploying rust-search-extension with
|
| Latest commit: |
c2f325d
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0f677850.rust-search-extension.pages.dev |
| Branch Preview URL: | https://cursor-fix-crates-index-db-d.rust-search-extension.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The scheduled crates-index workflow has been failing in
./scripts/deploy-crates-index.shon every daily run (latest: https://github.com/huhu/rust-search-extension/actions/runs/40390726860).db-dump0.7.x refuses the current https://static.crates.io/db-dump.tar.gz:crates.io replaced
versions.checksumwithversions.tar_sha256(and addedzip_sha256/zip_json_sha256).db-dump0.7.x deserializesversions.csvwithdeny_unknown_fieldsand still expectschecksum, so the first data row fails. The same runs also logged non-fatalunimplementedlines foroauth_github.csvandreserved_usernames.csv.db-dump0.8.0 (2026-07-03) learnedtar_sha256plus those two tables. 0.10.0 (2026-10-12) is the current release and matches the public columns in crates.io's dump config, includingreserved_crate_names.csv. It requires Rust 1.88 / edition 2024. The failing runner image (ubuntu-24.0420261012.334.1) already ships Rust 1.99.0, so the workflow does not need a toolchain pin.rust/src/tasks/crates.rsdid not need changes. It still only usescrate_downloads.crate_id/downloads,versions.crate_id/created_at/num, andcrates.id/name/description, which are unchanged.Cargo.lockstays gitignored, which is how this repo already resolves dependencies in CI.db-dump = "0.10.0"is the same caret-style requirement as the old0.7.1pin, so the workflow resolves 0.10.x.Verification
Built with Rust 1.99.1 (
cargo build) and ran the crates subcommand against the live dump (last-modified2026-10-27, 2,086,809,539 bytes):That is the same arguments as
./scripts/deploy-crates-index.sh(cargo run --release crates -p ... -d ...). Exit 0 in 195s. NounimplementedCSV warnings. Wrote/tmp/index.js(1,442,976 bytes, about 20,985 crates, same shape asextension/index/crates.js). Spot checks from the generated index: serde 1.0.229, tokio 1.54.1, regex 1.13.1, clap 4.6.7, axum 0.8.9.The upload half of
deploy-crates-index.shwas not run; it force-pushes thenowbranch and needsGITHUB_TOKEN.