renovate-bot:renovate/github-actionsrenovate-bot/gemini-cli-extensions-_-cloud-sql-postgresql:renovate/github-actionsCopy head branch name to clipboard
renovate-bot:renovate/github-actionsrenovate-bot/gemini-cli-extensions-_-cloud-sql-postgresql:renovate/github-actionsCopy head branch name to clipboard
This release updates the default lychee version from v0.23.0 to v0.24.2.
The main reason for this release is compatibility with the new lychee 0.24.x release artifacts. Starting with lychee v0.24.0, the archive layout changed, and the lychee binary may now be packaged inside a subdirectory. lychee-action now detects that layout automatically, so users can upgrade without changing their workflows.
If you use:
uses: lycheeverse/lychee-action@v2
you will get the new version once the floating v2 tag has been updated. If you pin exact versions, update to:
uses: lycheeverse/lychee-action@v2.9.0
What’s new from lychee v0.24.x
Better diagnostics
lychee now reports line and column numbers for detected links. This makes broken link reports easier to act on, especially in larger documentation sites or generated reports.
Text fragment checking
lychee can now check URL text fragments, such as links containing #:~:text=.... This helps catch links that point to a valid page but no longer points to the intended highlighted text.
Sitemap support
lychee can now read sitemap.xml inputs. This is useful for checking published websites or generated documentation sites where the sitemap is the easiest source of URLs to validate.
JUnit output
lychee now supports JUnit output. This makes it easier to integrate link checking results with CI systems and test reporting tools that understand JUnit XML.
Redirect and remap visibility
lychee can now show redirects and remaps more clearly. This helps explain why a URL was checked as a different final URL and makes debugging link-checking behavior easier.
Multiple config files
lychee now supports multiple configuration files and expanded config handling. This is useful for repositories that split documentation, website, or package-specific link-checking settings.
Timeout handling
lychee can now accept timeouts explicitly. This gives users more control over how strict their link checks should be for flaky or slow endpoints.
Fixes and reliability improvements
Fixed lychee 0.24.x archive compatibility
lychee-action now handles the new lychee release archive layout by detecting whether the lychee binary is inside a subdirectory.
This fixes compatibility with lychee 0.24.x.
More stable installation path
The action now installs lychee into $RUNNER_TEMP/lychee/bin instead of $HOME.
This avoids failures on runners where $HOME differs between composite action steps. In those environments, the action could add one directory to PATH but install the binary somewhere else, causing lychee: command not found.
Safer automatic lychee version updates
The workflow that checks for new lychee releases now guards against null release versions before creating update PRs. This prevents invalid automated PRs such as “Update lycheeVersion to null”.
renovate-bot
changed the title
chore(deps): update apache/skywalking-eyes digest to e0cc16d
chore(deps): update apache/skywalking-eyes digest to e910f72
May 5, 2026
renovate-bot
changed the title
chore(deps): update apache/skywalking-eyes digest to e910f72
chore(deps): update apache/skywalking-eyes digest to ab3d1fe
May 21, 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
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.
This PR contains the following updates:
Release Notes
lycheeverse/lychee-action (lycheeverse/lychee-action)v2.9.0
Compare Source
Summary
This release updates the default lychee version from v0.23.0 to v0.24.2.
The main reason for this release is compatibility with the new lychee 0.24.x release artifacts. Starting with lychee v0.24.0, the archive layout changed, and the lychee binary may now be packaged inside a subdirectory. lychee-action now detects that layout automatically, so users can upgrade without changing their workflows.
If you use:
you will get the new version once the floating v2 tag has been updated. If you pin exact versions, update to:
What’s new from lychee v0.24.x
Better diagnostics
lychee now reports line and column numbers for detected links. This makes broken link reports easier to act on, especially in larger documentation sites or generated reports.
Text fragment checking
lychee can now check URL text fragments, such as links containing #:~:text=.... This helps catch links that point to a valid page but no longer points to the intended highlighted text.
Sitemap support
lychee can now read sitemap.xml inputs. This is useful for checking published websites or generated documentation sites where the sitemap is the easiest source of URLs to validate.
JUnit output
lychee now supports JUnit output. This makes it easier to integrate link checking results with CI systems and test reporting tools that understand JUnit XML.
Redirect and remap visibility
lychee can now show redirects and remaps more clearly. This helps explain why a URL was checked as a different final URL and makes debugging link-checking behavior easier.
Multiple config files
lychee now supports multiple configuration files and expanded config handling. This is useful for repositories that split documentation, website, or package-specific link-checking settings.
Timeout handling
lychee can now accept timeouts explicitly. This gives users more control over how strict their link checks should be for flaky or slow endpoints.
Fixes and reliability improvements
Fixed lychee 0.24.x archive compatibility
lychee-action now handles the new lychee release archive layout by detecting whether the lychee binary is inside a subdirectory.
This fixes compatibility with lychee 0.24.x.
More stable installation path
The action now installs lychee into $RUNNER_TEMP/lychee/bin instead of $HOME.
This avoids failures on runners where $HOME differs between composite action steps. In those environments, the action could add one directory to PATH but install the binary somewhere else, causing lychee: command not found.
Safer automatic lychee version updates
The workflow that checks for new lychee releases now guards against null release versions before creating update PRs. This prevents invalid automated PRs such as “Update lycheeVersion to null”.
Dependency updates
Upstream lychee changelog
For the full lychee changelog, see:
What’s Changed
Full Changelog: lycheeverse/lychee-action@v2.8.0...v2.9.0
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.