Skip to content

link-validator: record summary - #3457

Merged
raboof merged 1 commit into
apache:mainfrom
raboof:link-validator-summary
Aug 21, 2026
Merged

raboof merged 1 commit into
apache:mainfrom
raboof:link-validator-summary

Conversation

@raboof

@raboof raboof commented Aug 21, 2026

Copy link
Copy Markdown
Member

make it easier to spot what failed

@pjfanning pjfanning left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@raboof

raboof commented Aug 21, 2026

Copy link
Copy Markdown
Member Author

failure seems to be a bind exception in JoinConfigCompatCheckerRollingUpdateSpec (must NOT be allowed to re-join a cluster if it has a new, additional configuration the others do not have and not the old), retriggering

@raboof
raboof merged commit f9a08e0 into apache:main Aug 21, 2026
15 of 16 checks passed
@raboof

raboof commented Aug 22, 2026

Copy link
Copy Markdown
Member Author

oops seems this version wasn't fully released yet (https://github.com/ennru/site-link-validator/actions/runs/32493027559/job/96804889973), let's wait a bit

@pjfanning

Copy link
Copy Markdown
Member

#3604 reverts this

pjfanning added a commit to pjfanning/incubator-pekko that referenced this pull request Oct 9, 2026
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 added a commit that referenced this pull request Oct 9, 2026
* ci: pin site-link-validator to 0.2.5

Motivation:
The Link Validator workflow has failed at the cs launch step since
#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 #3457

* docs: fix broken links reported by the link validator

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

* TEMP: run link validator on pull requests (revert before merge)

* Remove pull_request trigger from workflow

Removed pull_request trigger from link-validator workflow.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants