Skip to content

build(deps): bump peter-evans/create-issue-from-file from 5.0.1 to 6.0.0 #2658

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

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

build(deps): bump peter-evans/create-issue-from-file from 5.0.1 to 6.0.0 #2658

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .github/workflows/scheduled.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ jobs:

- name: Create issue
if: env.lychee_exit_code != 0
uses: peter-evans/create-issue-from-file@e8ef132d6df98ed982188e460ebb3b5d4ef3a9cd # v5
uses: peter-evans/create-issue-from-file@fca9117c27cdc29c6c4db3b86c48e4115a786710 # v6.0.0
Copy link
Copy Markdown
Contributor

@codacy-production codacy-production Bot May 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 HIGH RISK

Upgrading to v6.0.0 requires the issues: write permission for the GITHUB_TOKEN. Furthermore, the if condition on line 24 is broken as env.lychee_exit_code is undefined and the step will be skipped on job failure. Try running the following prompt in your coding agent: > Add permissions: issues: write to the workflow and update the check-broken-links job to use continue-on-error: true with a corrected if: failure() condition for issue creation.

with:
title: Broken link report
content-filepath: ./lychee/out.md
Expand Down Expand Up @@ -52,7 +52,7 @@ jobs:
python ./check-supported-tools.py > ${{ env.OUTPUT_FILE }}

- name: Create issue
uses: peter-evans/create-issue-from-file@e8ef132d6df98ed982188e460ebb3b5d4ef3a9cd # v5
uses: peter-evans/create-issue-from-file@fca9117c27cdc29c6c4db3b86c48e4115a786710 # v6.0.0
Copy link
Copy Markdown
Contributor

@codacy-production codacy-production Bot May 4, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 MEDIUM RISK

Starting in v6.0.0, this action fails if the file at content-filepath is empty. If the python script fails without output, this step will crash the workflow. Try running the following prompt in your coding agent: > Ensure the create-issue-from-file step in the check-supported-tools and check-security-tools jobs only runs when the output file is not empty.

if: ${{ failure() }}
with:
title: Missing supported tools report
Expand Down Expand Up @@ -83,7 +83,7 @@ jobs:
python ./check-security-tools.py > ${{ env.OUTPUT_FILE }}

- name: Create issue
uses: peter-evans/create-issue-from-file@e8ef132d6df98ed982188e460ebb3b5d4ef3a9cd # v5
uses: peter-evans/create-issue-from-file@fca9117c27cdc29c6c4db3b86c48e4115a786710 # v6.0.0
if: ${{ failure() }}
with:
title: Missing security tools report
Expand Down
Loading