-
Notifications
You must be signed in to change notification settings - Fork 0
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 lycheeverse/lychee-action action to v2 #95
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/major-github-actions
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports You could have same capabilities but better runtime performances if you request a new MegaLinter flavor. |
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
November 7, 2024 16:50
b1bf198
to
feeafd1
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
5 times, most recently
from
November 23, 2024 19:54
cb4eaa9
to
8db7475
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
December 19, 2024 16:19
8db7475
to
13c4e84
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
January 14, 2025 15:45
13c4e84
to
82e895e
Compare
renovate
bot
force-pushed
the
renovate/major-github-actions
branch
from
January 14, 2025 15:53
82e895e
to
2c073c2
Compare
Trivy image scan report
|
Package | ID | Severity | Installed Version | Fixed Version |
---|---|---|---|---|
libpython3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
No Misconfigurations found
Trivy image scan report
|
Package | ID | Severity | Installed Version | Fixed Version |
---|---|---|---|---|
libpython3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
No Misconfigurations found
Trivy image scan report
|
Package | ID | Severity | Installed Version | Fixed Version |
---|---|---|---|---|
libpython3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
libpython3.11-stdlib |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-7592 | HIGH | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2023-27043 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-6923 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-9287 | MEDIUM | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
python3.11-minimal |
CVE-2024-11168 | LOW | 3.11.2-6+deb12u4 | 3.11.2-6+deb12u5 |
No Misconfigurations found
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.2.0
Release Notes
lycheeverse/lychee-action (lycheeverse/lychee-action)
v2.2.0
: Version 2.2.0Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.2.0
v2.1.0
: Version 2.1.0Compare Source
What's Changed
failIfEmpty
by @LitoMore in https://github.com/lycheeverse/lychee-action/pull/261New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.1.0
v2.0.2
: Version 2.0.2Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.2
v2.0.1
: Version 2.0.1Compare Source
What's Changed
New Contributors
Full Changelog: lycheeverse/lychee-action@v2...v2.0.1
v2.0.0
: Version 2.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@master
branch don't need to make any changes, asfail: true
has been the default there for a while.fail
tofalse
when 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:
For a more detailed description of the technical aspects behind these changes, please see the full changelog below.
What's Changed
failIfEmpty
argument (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 - "* 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.
This PR was generated by Mend Renovate. View the repository job log.