Skip to content

Releases: lycheeverse/lychee-action

Version 2.2.0

19 Dec 14:42
@mre mre
f796c8b
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2...v2.2.0

Version 2.1.0

07 Nov 12:52
@mre mre
f81112d
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2...v2.1.0

Version 2.0.2

14 Oct 08:14
@mre mre
7cd0af4
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2...v2.0.2

Version 2.0.1

11 Oct 22:54
@mre mre
2bb2326
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v2...v2.0.1

Version 2.0.0

08 Oct 12:18
@mre mre
7da8ec1
Compare
Choose a tag to compare

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:

  • Update to version 2 of this action to apply this change.
  • Users of the lychee-action@master branch don't need to make any changes, as fail: true has been the default there for a while.
  • If you prefer the old behavior, explicitly set fail to false when updating:
- name: Link Checker
  id: lychee
  uses: lycheeverse/lychee-action@v2
  with:
    fail: false  # Don't fail action on broken links

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:

  • If you expect links to be found in your pipeline run, you don't need to do anything.
  • If you expect no links in your pipeline run, you can opt out like this:
- name: Link Checker
  id: lychee
  uses: lycheeverse/lychee-action@v2
  with:
    failIfEmpty: false  # Don't fail action if no links were found

For a more detailed description of the technical aspects behind these changes, please see the full changelog below.

What's Changed

New Contributors

Full Changelog: v1...v1.11.0

Version 1.10.0

25 Apr 10:45
@mre mre
2b973e8
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.9.3...v1.10.0

Version 1.0.0

13 Dec 15:11
@mre mre
2b973e8
Compare
Choose a tag to compare

First release of the lychee Github action — an action to check for broken links in Markdown, HTML, and text files using lychee, a fast link checker written in Rust.

Version 1.9.3

29 Jan 11:26
@mre mre
c053181
Compare
Choose a tag to compare

What's Changed

  • Bugfix: Pass custom token as input argument to action by @mre in #222
    Previously, the name of the token was incorrect, leading to no token being used if the user specified with: [token: ...].
    Thanks to @tobon4 for pointing this out.

Full Changelog: v1...v1.9.3

Version 1.9.2

26 Jan 15:46
@mre mre
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1...v1.9.2

Version 1.9.1

10 Jan 00:10
@mre mre
c3089c7
Compare
Choose a tag to compare

This is a hotfix release which restores the behavior of the accept config parameter.
Integers are accepted again as status codes.

accept = [200, 201, 202, 203, 429]

is equivalent to

accept = ["200..=203", 429]

Integers and strings (e.g. for ranges) can be mixed.