Skip to content

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

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/peter-evans/create-issue-from-file-6.0.0
Open

build(deps): bump peter-evans/create-issue-from-file from 5.0.1 to 6.0.0#2658
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/github_actions/peter-evans/create-issue-from-file-6.0.0

Conversation

@dependabot

@dependabotdependabotBot commented on behalf of githubMay 4, 2026

Copy link
Copy Markdown
Contributor

Bumps peter-evans/create-issue-from-file from 5.0.1 to 6.0.0.

Release notes

Sourced from peter-evans/create-issue-from-file's releases.

Create Issue From File v6.0.0

⚙️ Requires Actions Runner v2.327.1 or later if you are using a self-hosted runner for Node 24 support.

What's Changed

... (truncated)

Commits

@dependabotdependabotBot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels May 4, 2026
@dependabot
dependabotBot requested a review from a team as a code ownerMay 4, 2026 12:10
@dependabotdependabotBot added dependencies Pull requests that update a dependency file github_actions Pull requests that update Github_actions code labels May 4, 2026
@codacy-production

codacy-productionBot commented May 4, 2026

Copy link
Copy Markdown
Contributor

Up to standards ✅

🟢 Issues0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

Run reviewer

TIP This summary will be updated as you push new changes.

@codacy-productioncodacy-productionBot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull Request Overview

While the version bump itself is straightforward, the upgrade to v6.0.0 introduces two breaking changes that require manual configuration updates: the need for explicit issues: write permissions and a new default failure behavior when input files are empty.

Furthermore, the existing workflow logic for detecting job failures via custom environment variables is currently non-functional, meaning the issue creation step would be skipped even if permissions were correct. These issues must be addressed to ensure the scheduled reports continue to function after the upgrade.

Test suggestions

  • Verify issue creation for 'Broken link report' succeeds on workflow failure with version 6.0.0.
  • Verify issue creation for 'Missing supported tools report' succeeds on workflow failure with version 6.0.0.
  • Verify issue creation for 'Missing security tools report' succeeds on workflow failure with version 6.0.0.
Prompt proposal for missing tests
Consider implementing these tests if applicable:
1. Verify issue creation for 'Broken link report' succeeds on workflow failure with version 6.0.0.
2. Verify issue creation for 'Missing supported tools report' succeeds on workflow failure with version 6.0.0.
3. Verify issue creation for 'Missing security tools report' succeeds on workflow failure with version 6.0.0.

TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback

- 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

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.


- 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

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.

Bumps [peter-evans/create-issue-from-file](https://github.com/peter-evans/create-issue-from-file) from 5.0.1 to 6.0.0.
- [Release notes](https://github.com/peter-evans/create-issue-from-file/releases)
- [Commits](peter-evans/create-issue-from-file@e8ef132...fca9117)
---
updated-dependencies:
- dependency-name: peter-evans/create-issue-from-file
dependency-version: 6.0.0
dependency-type: direct:production
update-type: version-update:semver-major
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabotBotforce-pushed the dependabot/github_actions/peter-evans/create-issue-from-file-6.0.0 branch from c85a259 to 0771cbaCompareMay 18, 2026 13:31
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesPull requests that update a dependency filegithub_actionsPull requests that update Github_actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants