feat: upgrade to linkinator 7.4.1 and improve fragment validation error messaging - #219
Merged
Conversation
…gment validation Updated linkinator to version 7.4.1 which includes GitHub-style heading ID support for fragment validation. Enhanced error reporting to show clear reasons when links fail, especially for 200 responses with missing anchors. Now displays specific failure reasons (e.g., "Fragment not found") in both console output and job summary tables. Addresses feedback from #217 where HTTP 200 responses with broken anchors were confusingly reported. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Added a test link with a non-existent anchor (#this-anchor-does-not-exist) to verify the new fragment validation error messaging works correctly in CI. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Enable checkFragments option in CI workflow to test the new fragment validation error messaging on pull requests. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Updated status code display to show 'x' for fragment validation failures, matching linkinator CLI behavior. This makes it clearer that the failure is due to a missing anchor rather than an HTTP error. Changes: - Added isFragmentFailure() helper to detect fragment validation errors - Added getDisplayStatus() helper to return 'x' for fragment failures - Updated console output, job summary table, and error messages to use new display status 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
Removed the intentional bad fragment link that was added for testing purposes. The PR is now ready for review with all links passing validation. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This was referenced Jul 22, 2026
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.
Summary
Changes Made
getFailureReason()helper to extract user-friendly error messages[200] url - Fragment not foundinstead of just[200] urlTesting
This PR intentionally includes a broken fragment link in the README to demonstrate the new error messaging. The CI should fail and display:
Addresses feedback from #217 where HTTP 200 responses with broken anchors were confusingly reported.
🤖 Generated with Claude Code