Skip to content

Releases

v0.3.0

Choose a tag to compare

@github-actions github-actions released this 11 Nov 23:26
Immutable release. Only release title and notes can be modified.
  • A permanent redirect that only adds query parameters or a locale path segment (/en-gb/) no
    longer rewrites the link: it stays as written and counts as OK, so a report-only run whose
    only findings were such redirects now exits 0.
  • A permanent fix now stops before a noise step: /old to /new to /new?language=en_US is
    rewritten to /new.
  • A fix drops the utm_* parameters the redirect added, keeping any the link had. Detection may
    GET the stripped URL once more, and the strip stands only when that page has the same title.
  • A link whose fix would now be the site root (/promo to / to /en-gb/) is
    SUSPECT redirect to root instead of rewritten, and gets a snapshot lookup like any suspect.

v0.2.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 23:00
Immutable release. Only release title and notes can be modified.
  • A 404 or 410 is now UNVERIFIABLE instead of DEAD when the host's root answers 404 or 410
    too, as on a bot wall that answers every path alike. Detection may GET a host's root once more.
  • A redirect chain that ends with no usable Location after a 301 or 308 now says
    no location after <statuses> to <target>, naming where the permanent redirect ended.

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 20:35
Immutable release. Only release title and notes can be modified.
  • Fewer false soft-404s on sites unlike a personal blog:
    • A link is no longer suspect when the made-up probe URL redirects to the link itself, as on
      sites that find an article by its ID and ignore the rest of the URL.
    • A shared <title> no longer makes a link suspect when the two pages' text differs.
  • A link that looks like a soft-404 is now UNVERIFIABLE instead of suspect when the host's root
    gets the same page as the probe (probe: every URL gets the same page) or the page asks for
    JavaScript (probe: page needs JavaScript). Detection may GET a host's root once.
  • Snapshot lookups run for dead links first, then suspects, so a deadline cuts off suspects first.
  • The action takes a path input (default .) for a site in a subfolder.

v0.1.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:40
Immutable release. Only release title and notes can be modified.
  • The action is named "rotguard link checker & fixer" so it can be listed on the GitHub
    Marketplace, where the name "rotguard" is taken by a user account. uses: rdiachenko/rotguard@v0
    is unchanged.

v0.1.0

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:17
Immutable release. Only release title and notes can be modified.

First public release.

  • Checks the outbound links of a markdown site's sources: markdown links, reference definitions,
    autolinks, raw HTML href/src, bare URLs and TOML and YAML front matter.
  • Classifies each link as permanent or temporary redirect, dead, suspect (soft-404),
    unverifiable or blocked (bot wall).
  • Proposes a fix for permanent redirects and dead links, the latter from the Wayback Machine
    snapshot closest to the page's date. --apply writes the safe fixes back into the files.
  • Reports as text, JSON, HTML or markdown; --strict and --quiet flags.
  • A composite GitHub Action that runs --apply and outputs a markdown report for a pull request.
  • Every release publishes static Linux binaries for x86_64 and arm64 on the GitHub releases page.
  • The action pinned to @v0 downloads the release binary instead of building rotguard; other
    refs build from source as before.
  • Without system CA certificates rotguard prints a message and exits 2 instead of panicking.