Skip to content

v2.2.1

  • v2.2.1
  • 7f76740

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
release: v2.2.1 — eleven crates.io pages stop 404ing (#68)
  • v2.2.1
  • 7f76740

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode
@vyncint vyncint tagged this 10 Sep 11:11 
All eleven crates set `readme = "../../README.md"`, so the root README ships as each one's readme, and crates.io rewrites a relative link against the crate's directory rather than the repository root. `docs/SAFETY.md` was served as `.../blob/HEAD/crates/launchbound-space/docs/SAFETY.md`, which does not exist. The same eight links were dead on all eleven published 2.2.0 pages, checked crate by crate — including docs/SAFETY.md, the document the README calls "the product".

Nothing here could see it: the same file renders correctly on GitHub, where it really is at the root.

Absolute links are the only shape correct from both roots. The Action's is `tree/main/action`, not `blob/`, because it is a directory — GitHub 301s the wrong form rather than failing, so it would have "worked" and still been the wrong URL to publish.

`scripts/check-readme-links.sh` in `just ci` refuses a relative link, checks every target exists in the checkout, and holds `blob` versus `tree` to what the path actually is — the last being the one a status-code checker cannot see. All three failure paths were exercised.

Future releases only: crates.io renders each version's readme as published, so the 2.2.0 pages stay broken.

Signed-off-by: Vyncint Ng <115854244+vyncint@users.noreply.github.com>
Assets 2
Loading