feat(github-action)!: Update lycheeverse/lychee-action action to v2.9.0 - #868
Open
chii-bot[bot] wants to merge 1 commit into
Open
feat(github-action)!: Update lycheeverse/lychee-action action to v2.9.0#868chii-bot[bot] wants to merge 1 commit into
chii-bot[bot] wants to merge 1 commit into
Conversation
Contributor
Author
MegaLinter status: ❌ ERROR
See errors details in artifact MegaLinter reports on CI Job page |
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
October 11, 2024 23:19
11bc4c9 to
bf068dd
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
October 14, 2024 08:25
bf068dd to
9d54e9c
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
November 7, 2024 13:25
9d54e9c to
4e44ba8
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
December 19, 2024 15:21
4e44ba8 to
ef8a154
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
February 4, 2025 23:19
ef8a154 to
0923b82
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
March 31, 2025 12:41
0923b82 to
cd22300
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
May 9, 2025 10:23
cd22300 to
e848651
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
August 7, 2025 11:23
e848651 to
b2005e3
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
August 22, 2025 10:23
b2005e3 to
b9d228d
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
August 25, 2025 11:20
b9d228d to
1d0bca7
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
October 29, 2025 16:11
1d0bca7 to
09e9110
Compare
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
February 25, 2026 08:22
09e9110 to
94c0116
Compare
| datasource | package | from | to | | ----------- | ------------------------- | ------- | ------ | | github-tags | lycheeverse/lychee-action | v1.10.0 | v2.9.0 |
chii-bot
Bot
force-pushed
the
renovate/lycheeverse-lychee-action-2.x
branch
from
July 9, 2026 16:57
94c0116 to
3b70c07
Compare
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.
This PR contains the following updates:
v1.10.0->v2.9.0⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
lycheeverse/lychee-action
v2.9.0Compare Source
Summary
This release updates the default lychee version from
v0.23.0tov0.24.2.The main reason for this release is compatibility with the new lychee
0.24.xrelease artifacts. Starting with lycheev0.24.0, the archive layout changed, and thelycheebinary may now be packaged inside a subdirectory.lychee-actionnow detects that layout automatically, so users can upgrade without changing their workflows.If you use:
you will get the new version once the floating
v2tag has been updated. If you pin exact versions, update to:What’s new from lychee
v0.24.xBetter 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.xmlinputs. 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.xarchive compatibilitylychee-actionnow handles the new lychee release archive layout by detecting whether thelycheebinary 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/bininstead of$HOME.This avoids failures on runners where
$HOMEdiffers between composite action steps. In those environments, the action could add one directory toPATHbut install the binary somewhere else, causinglychee: command not found.Safer automatic lychee version updates
The workflow that checks for new lychee releases now guards against
nullrelease versions before creating update PRs. This prevents invalid automated PRs such as “Update lycheeVersion to null”.Dependency updates
actions/checkoutfromv6tov7actions/cachefromv5tov6Upstream lychee changelog
For the full lychee changelog, see:
What’s Changed
$RUNNER_TEMPinstead of$HOMEby @mre in https://github.com/lycheeverse/lychee-action/pull/338Full Changelog: lycheeverse/lychee-action@v2.8.0...v2.9.0
v2.8.0Compare Source
What's Changed
--root-dirinstead of the deprecated--baseby @mre in https://github.com/lycheeverse/lychee-action/pull/315New Contributors
Full Changelog: lycheeverse/lychee-action@v2.7.0...v2.8.0
v2.7.0Compare Source
Breaking changes
If you're using
--base, you must now provide either a URL (with scheme) or an absolute local path. Seelychee --helpfor more information. If you want to resolve root-relative links in local files, also see--root-dir.What's Changed
See https://github.com/lycheeverse/lychee/releases/tag/lychee-v0.21.0 for the lychee changelog.
Full Changelog: lycheeverse/lychee-action@v2...v2.7.0
v2.6.1Compare Source
What's Changed
Full Changelog: lycheeverse/lychee-action@v2...v2.6.1
v2.6.0Compare Source
What's Changed
Full Changelog: lycheeverse/lychee-action@v2...v2.6.0
v2.5.0Compare Source
Summary
Most notably with this release the deprecated
--exclude-mailflag was removed and the behavior of the--acceptflag was updated. Previously, status codes such as 200 OK were always accepted. Now they are only accepted by default. This means providing the argument--accept 201now rejects status code 200 OK.What's Changed
Full Changelog: lycheeverse/lychee-action@v2...v2.5.0
v2.4.1Compare Source
What's Changed
lycheeversion check by @mondeja in https://github.com/lycheeverse/lychee-action/pull/288Full Changelog: lycheeverse/lychee-action@v2...v2.4.1
v2.4.0Compare Source
What's Changed
lychee now has a new task output, which allows to track which links got fixed more easily.
It looks like this:
[test.html]:
Each broken link has a checkbox that can be ticked off once fixed. Credit goes to @Arteiii for the idea and the implementation.
See #274 for more information.
Update To latest lychee Release by @Arteiii in https://github.com/lycheeverse/lychee-action/pull/279
Add
workingDirectoryargument by @mre in https://github.com/lycheeverse/lychee-action/pull/283New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.4.0
v2.3.0Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.3.0
v2.2.0Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.2.0
v2.1.0Compare Source
What's Changed
failIfEmptyby @LitoMore in https://github.com/lycheeverse/lychee-action/pull/261New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.1.0
v2.0.2Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.2
v2.0.1Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.1
v2.0.0Compare Source
Breaking Changes
Note: This release improves the action's robustness by changing default behaviors. Changes are only required if you want to opt out of the new failure conditions. Most users won't need to modify their existing configurations.
Fail pipeline on error by default
We've changed the default behavior: pipelines will now fail on broken links automatically. This addresses user feedback that not failing on broken links was unexpected (see issue #71).
What you need to do:
lychee-action@masterbranch don't need to make any changes, asfail: truehas been the default there for a while.failtofalsewhen updating:Fail pipeline if no links were found
Similar to the above change, we now fail the pipeline if no links are found during a run. This helps warn users about potential configuration issues.
What you need to do:
Exit code handling
In this version, we changed the environment variable for the lychee exit code from
GITHUB_ENVtoGITHUB_OUTPUT.Please update your scripts. For more details, see https://github.com/lycheeverse/lychee-action/pull/245.
For a more detailed description of the technical aspects behind these changes, please see the full changelog below.
What's Changed
failIfEmptyargument (fixes #84) by @mre in https://github.com/lycheeverse/lychee-action/pull/86New Contributors
Full Changelog: lycheeverse/lychee-action@v1...v1.11.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.