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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update lycheeverse/lychee-action action to v2 #95

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(deps): update lycheeverse/lychee-action action to v2 #95

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 1, 2024 •
edited
Loading

This PR contains the following updates:

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

Release Notes

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

v2.2.0: Version 2.2.0

Compare Source

What's Changed

New Contributors

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

v2.1.0: Version 2.1.0

Compare Source

What's Changed

New Contributors

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

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 - "* 0-3 1 * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

@github-actions GitHub Actions
Copy link

github-actions bot commented Nov 1, 2024 •
edited
Loading

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 7 0 0.09s
✅ COPYPASTE jscpd yes no 1.15s
✅ DOCKERFILE hadolint 1 0 0.06s
✅ JSON jsonlint 3 0 0.6s
✅ JSON prettier 3 0 0.58s
✅ JSON v8r 3 0 3.07s
✅ PYTHON bandit 1 0 0.93s
✅ PYTHON black 1 0 0.86s
✅ PYTHON flake8 1 0 1.2s
✅ PYTHON isort 1 0 0.15s
✅ PYTHON mypy 1 0 2.85s
✅ PYTHON pylint 1 0 2.5s
✅ PYTHON pyright 1 0 6.47s
✅ PYTHON ruff 1 0 0.01s
✅ REPOSITORY checkov yes no 19.98s
✅ REPOSITORY devskim yes no 1.31s
✅ REPOSITORY dustilock yes no 0.01s
✅ REPOSITORY gitleaks yes no 0.69s
✅ REPOSITORY git_diff yes no 0.0s
✅ REPOSITORY grype yes no 13.27s
✅ REPOSITORY kics yes no 4.0s
✅ REPOSITORY secretlint yes no 0.89s
✅ REPOSITORY syft yes no 1.46s
✅ REPOSITORY trivy yes no 7.95s
✅ REPOSITORY trivy-sbom yes no 0.12s
✅ REPOSITORY trufflehog yes no 3.05s
✅ YAML prettier 9 0 0.53s
✅ YAML v8r 9 0 8.46s
✅ YAML yamllint 9 0 0.55s

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

MegaLinter is graciously provided by OX Security

@renovate renovate bot force-pushed the renovate/major-github-actions branch from b1bf198 to feeafd1 Compare November 7, 2024 16:50
@renovate renovate bot force-pushed the renovate/major-github-actions branch 5 times, most recently from cb4eaa9 to 8db7475 Compare November 23, 2024 19:54
@renovate renovate bot force-pushed the renovate/major-github-actions branch from 8db7475 to 13c4e84 Compare December 19, 2024 16:19
@github-actions GitHub Actions
Copy link

Trivy image scan report

ghcr.io/miracum/github-reusable-workflow-without-test-image:pr-95 (debian 12.8)

No Vulnerabilities found

No Misconfigurations found

@github-actions GitHub Actions
Copy link

Trivy image scan report

ghcr.io/miracum/github-reusable-workflow:pr-95 (debian 12.8)

No Vulnerabilities found

No Misconfigurations found

@github-actions GitHub Actions
Copy link

Trivy image scan report

ghcr.io/miracum/github-reusable-workflow-with-fixed-image-tags:v1.2.3-beta.123 (debian 12.8)

No Vulnerabilities found

No Misconfigurations found

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants