Repository navigation
ci: pin site-link-validator to 0.2.5 and fix broken doc links - #3604
Merged
Merged
Conversation
pjfanning
marked this pull request as draft
October 9, 2026 09:05
Motivation: The Link Validator workflow has failed at the cs launch step since apache#3457 because site-link-validator 0.3.0 was never published to Maven Central (its release job failed with a Sonatype 401). Modification: Use 0.2.5, the latest published version, and drop the $GITHUB_STEP_SUMMARY argument that 0.2.5 does not support. Result: The link validator runs again. Tests: - Link Validator workflow run on the PR References: Refs apache#3457
pjfanning
force-pushed
the
ci-link-validator-0.2.5
branch
from
October 9, 2026 09:27
53ba076 to
6adabef
Compare
raboof
approved these changes
Oct 9, 2026
raboof
left a comment
Member
There was a problem hiding this comment.
👍 sorry about being trigger-happy with 0.3.0
Motivation: The link validator reports 404s for moved pages and 403s from sites that block automated clients. Modification: - Point Maven Central search links at Sonatype Central - Link the logback AsyncAppender manual section (apidocs were removed) - Point the pekko-management extref at the 2.0 docs, since the rolling-updates page is not in the current docs - Update the moved Datadog stolen-CPU article URL - Ignore sites that return 403 to bots (bugs.openjdk.org, medium, stackoverflow, waldo.scholars.harvard.edu) and the unpublished scala.runtime Scaladoc Result: The link validator reports no failure responses. Tests: - Link Validator workflow run on the PR References: None - link validator maintenance
pjfanning
force-pushed
the
ci-link-validator-0.2.5
branch
from
October 9, 2026 09:33
6adabef to
796622e
Compare
Removed pull_request trigger from link-validator workflow.
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
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.
Motivation
The scheduled Link Validator workflow has failed every week since #3457 bumped
site-link-validatorto 0.3.0 (example run):0.3.0 and 0.4.0 are tagged on GitHub, but both release jobs failed to upload to Sonatype Central (401). The latest version on Maven Central is 0.2.5. With 0.2.5 in place, the validator reported 13 links with failure responses.
Modification
$GITHUB_STEP_SUMMARYargument, which 0.2.5 does not support.current.ignore-prefixes. Also ignore thescala/runtimeScaladoc, which is not published; this replaces the individualAbstractFunctionNentries.pull_requesttrigger so the validator runs on this PR. It must be dropped before merge.Result
The Link Validator workflow runs again, and the links it reported are fixed or ignored.
Tests
pull_requesttrigger)References
Refs #3457