feat(github-action)!: Update lycheeverse/lychee-action action to v2.1.0

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
lycheeverse/lychee-action	action	major	v1.10.0 -> v2.1.0

---

Release Notes

lycheeverse/lychee-action (lycheeverse/lychee-action)

v2.1.0: Version 2.1.0

Compare Source

What's Changed

• Add missing argument failIfEmpty by @​LitoMore in https://github.com/lycheeverse/lychee-action/pull/261
• Fix bugs about the exit code by @​YDX-2147483647 in https://github.com/lycheeverse/lychee-action/pull/262
• Bump lychee version to 0.17.0 by @​mre in https://github.com/lycheeverse/lychee-action/pull/263

New Contributors

• @​LitoMore made their first contribution in https://github.com/lycheeverse/lychee-action/pull/261
• @​YDX-2147483647 made their first contribution in https://github.com/lycheeverse/lychee-action/pull/262

Full Changelog: lycheeverse/lychee-action@v2...v2.1.0

v2.0.2: Version 2.0.2

Compare Source

What's Changed

• Fix a typos by @​szepeviktor in https://github.com/lycheeverse/lychee-action/pull/257
• Document and use correct permissions in the GitHub workflows by @​dscho in https://github.com/lycheeverse/lychee-action/pull/258
• Add security policy by @​mondeja in https://github.com/lycheeverse/lychee-action/pull/259

New Contributors

• @​szepeviktor made their first contribution in https://github.com/lycheeverse/lychee-action/pull/257
• @​mondeja made their first contribution in https://github.com/lycheeverse/lychee-action/pull/259

Full Changelog: lycheeverse/lychee-action@v2...v2.0.2

v2.0.1: Version 2.0.1

Compare Source

What's Changed

• Don't remove the lychee config file by @​dmathieu in https://github.com/lycheeverse/lychee-action/pull/255
• Bump lycheeverse/lychee-action from 1 to 2 by @​dependabot in https://github.com/lycheeverse/lychee-action/pull/252
• Fix variable name in docs by @​kdeldycke in https://github.com/lycheeverse/lychee-action/pull/253

New Contributors

• @​dmathieu made their first contribution in https://github.com/lycheeverse/lychee-action/pull/255

Full Changelog: lycheeverse/lychee-action@v2...v2.0.1

v2.0.0: Version 2.0.0

Compare 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:

• 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

• feat: change to use the full version tag with v-* prefix by @​kemingy in https://github.com/lycheeverse/lychee-action/pull/204
• Add failIfEmpty argument (fixes #​84) by @​mre in https://github.com/lycheeverse/lychee-action/pull/86
• Fail pipeline on error by default (fixes #​71) by @​mre in https://github.com/lycheeverse/lychee-action/pull/85
• Exit in case output is set in args and action input by @​mre in https://github.com/lycheeverse/lychee-action/pull/227
• v1 will automatically use latest version by @​jacobdalamb in https://github.com/lycheeverse/lychee-action/pull/228
• Remove unneeded text by @​jacobdalamb in https://github.com/lycheeverse/lychee-action/pull/229
• Clarify README.md defaults by @​paddyroddy in https://github.com/lycheeverse/lychee-action/pull/230
• Adjust for new asset naming scheme by @​dscho in https://github.com/lycheeverse/lychee-action/pull/234
• Test various lychee versions by @​mre in https://github.com/lycheeverse/lychee-action/pull/235
• Better cleanup of old lychee assets by @​mre in https://github.com/lycheeverse/lychee-action/pull/237
• Bump peter-evans/create-issue-from-file from v4 to v5 by @​AndreiCherniaev in https://github.com/lycheeverse/lychee-action/pull/241
• Remove dots from table by @​AndreiCherniaev in https://github.com/lycheeverse/lychee-action/pull/242
• README: update actions/cache to v4 by @​sebastiaanspeck in https://github.com/lycheeverse/lychee-action/pull/243
• Set exit_code correctly as output by @​sebastiaanspeck in https://github.com/lycheeverse/lychee-action/pull/245
• action: fix failing CI by @​sebastiaanspeck in https://github.com/lycheeverse/lychee-action/pull/246
• Split up steps in action by @​mre in https://github.com/lycheeverse/lychee-action/pull/248
• Bump version to 0.16.x, respect new tag names by @​mre in https://github.com/lycheeverse/lychee-action/pull/249
• Test latest lychee version tag by @​mre in https://github.com/lycheeverse/lychee-action/pull/236

New Contributors

• @​kemingy made their first contribution in https://github.com/lycheeverse/lychee-action/pull/204
• @​paddyroddy made their first contribution in https://github.com/lycheeverse/lychee-action/pull/230
• @​dscho made their first contribution in https://github.com/lycheeverse/lychee-action/pull/234
• @​AndreiCherniaev made their first contribution in https://github.com/lycheeverse/lychee-action/pull/241
• @​sebastiaanspeck made their first contribution in https://github.com/lycheeverse/lychee-action/pull/243

Full Changelog: lycheeverse/lychee-action@v1...v1.11.0

---

Configuration

📅 Schedule: Branch creation - "on saturday" (UTC), 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.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[jsaveker]

Here is an automated review from ChatGPT of this pull request.

There were no direct security issues that could be identified from this specific git diff. This change simply updates the version of a GitHub Action (lycheeverse/lychee-action) from v1.10.0 to v2.0.1.

However, it's essential to consider the following best practices when making such updates to mitigate potential security risks:

1. Review Changelog: Before updating any dependencies, especially actions used in CI/CD pipelines, review the changelog or release notes of the new version to ensure there are no breaking changes or newly introduced features that may alter the security posture of your workflow.

2. Check the Source: Verify the source of the new version (2bb232618be239862e31382c5c0eaeba12e5e966) to ensure it's from the same, trusted maintainer or organization, and not from a fork that could potentially introduce malicious code.

3. Least Privilege: The workflow uses a GITHUB_TOKEN which is automatically generated by GitHub for each run. Ensure that the token permissions are set to the minimum required for the task at hand to avoid excessive privileges that could be abused if the action or the repository is compromised.

4. Regularly Update Actions: Continuous updating of actions like these is good practice to ensure that you benefit from the latest features, bug fixes, and security patches. Always ensure that updates are tested in a controlled environment before being merged into your main branch to minimize potential disruptions.

Given the context provided, there is no need for a specific fix related to the changes in the git diff. However, adhering to the best practices mentioned above will help maintain the security and reliability of your CI/CD pipeline.