Link queued crates to exact versions#3408
Open
Bortlesboat wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
the
S-waiting-on-review
GuillaumeGomez
approved these changes
Jul 13, 2026
Member
|
Looks good to me, thanks! Gonna wait for @syphar to be back to confirm it's all good. |
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
2 participants
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.
Queued releases now link to their exact crates.io version pages instead of the crate-level page, which always resolves to the latest release.
This applies consistently to the normal build queue and the expandable automated rebuild queue. The existing render tests now assert the full version-specific
hreffor every queued item.Fixes #1009.
Validation:
cargo test -p docs_rs_web --no-runcargo clippy -p docs_rs_web --tests -- -D warningscargo fmt --all -- --checkgit diff --checkThe targeted queue tests compile locally but require the repository's PostgreSQL test service (
DOCSRS_DATABASE_URL) to execute. Docker Desktop is not running on this Windows host, so local execution stops during sharedTestEnvironmentsetup before reaching any assertions; upstream CI has the required service.