Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update github-actions (major) #54

Merged
merged 1 commit into from
Oct 20, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 1, 2024

This PR contains the following updates:

Package Type Update Change
lycheeverse/lychee-action action major v1.10.0 -> v2.0.2
ubuntu github-runner major 22.04 -> 24.04

Release Notes

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

v2.0.2: Version 2.0.2

Compare Source

What's Changed
New Contributors

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

v2.0.1: Version 2.0.1

Compare Source

What's Changed
New Contributors

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
New Contributors

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


Configuration

📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

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

Copy link

github-actions bot commented Oct 1, 2024

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 3 0 0.07s
✅ GROOVY npm-groovy-lint 2 0 8.29s
✅ JAVA checkstyle 4 0 2.82s
✅ JSON jsonlint 1 0 0.21s
✅ JSON prettier 1 0 0.4s
✅ JSON v8r 1 0 2.44s
✅ MARKDOWN markdownlint 2 0 0.37s
✅ MARKDOWN markdown-table-formatter 2 0 0.29s
✅ REPOSITORY checkov yes no 13.7s
✅ REPOSITORY dustilock yes no 0.01s
✅ REPOSITORY gitleaks yes no 0.15s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY grype yes no 14.62s
✅ REPOSITORY kics yes no 2.21s
✅ REPOSITORY secretlint yes no 0.7s
✅ REPOSITORY syft yes no 2.12s
✅ REPOSITORY trivy yes no 8.29s
✅ REPOSITORY trivy-sbom yes no 0.63s
✅ REPOSITORY trufflehog yes no 5.28s
✅ XML xmllint 1 0 0.01s
✅ YAML prettier 4 0 0.54s
✅ YAML v8r 4 0 5.82s
✅ YAML yamllint 4 0 0.56s

See detailed report in MegaLinter reports

You could have the same capabilities but better runtime performances if you use a MegaLinter flavor:

MegaLinter is graciously provided by OX Security

@renovate renovate bot force-pushed the renovate/major-github-actions branch from f5b1a86 to d6985e4 Compare October 8, 2024 13:39
@renovate renovate bot changed the title chore(deps): update dependency ubuntu to v24 chore(deps): update github-actions (major) Oct 8, 2024
@renovate renovate bot force-pushed the renovate/major-github-actions branch from d6985e4 to 664c558 Compare October 12, 2024 01:08
@renovate renovate bot force-pushed the renovate/major-github-actions branch from 664c558 to 5a6e1e0 Compare October 14, 2024 09:20
@chgl chgl merged commit 6fd5379 into master Oct 20, 2024
8 checks passed
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.

1 participant