Fix three broken internal links - #116
Closed
vpetersson-bot wants to merge 1 commit into
Closed
Conversation
Found by a site-wide link audit of the built output (331 pages). All three predate this change and 404 today: - posts/2026-01-23-...-attestations.md used a /blog/ prefix for a post permalink; the permalink format is /:year/:month/:day/:title/ - compliance/fda-medical-device.md linked /blog/fda-medical-device-sbom- requirements/ instead of the post's dated permalink - faq/why-do-i-need-an-sbom.md linked /compliance/fda/, which does not exist; the page is /compliance/fda-medical-device/ Verified: dprint clean, Hugo builds, and a re-run of the audit reports zero broken internal links across the site.
This was referenced Jul 30, 2026
Contributor
Author
|
Superseded by #118, which folds this together with the other two v26.7.1 site changes into a single PR. The commit is carried over unchanged (cherry-picked with |
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
1 participant
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.
Found while auditing the site against the v26.7.1 release. All three 404 on the live site today and predate this change.
content/posts/2026-01-23-…-attestations.md:46/blog/2026/01/20/announcing-sbomify-action-v0-11-…//2026/01/20/announcing-sbomify-action-v0-11-…/content/compliance/fda-medical-device.md:62/blog/fda-medical-device-sbom-requirements//2026/01/09/fda-medical-device-sbom-requirements/content/faq/why-do-i-need-an-sbom.md:28/compliance/fda//compliance/fda-medical-device/The first two use a
/blog/prefix that isn't the permalink format (/:year/:month/:day/:title/perhugo.toml). The third points at a page that doesn't exist.Verification
Audited every
hrefin the built output (331 pages), resolving each internal link againstpublic/:dprint checkclean, Hugo builds.Worth a look separately
CI runs lychee in
lint.yml, but that workflow only triggers on PRs touching.md/.d2/layouts//content/etc. These three slipped through — either they landed before lychee was added, or its config skips relative internal links. Might be worth confirming lychee actually resolves internal links, otherwise this class of breakage stays invisible.