Skip to content

build(deps): bump actions/upload-artifact from 5 to 6 #90

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 actions/upload-artifact from 5 to 6 #90

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
2 changes: 1 addition & 1 deletion .github/workflows/oss-fuzz.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ jobs:
fuzz-seconds: 600
dry-run: false
- name: Upload Crash
uses: actions/upload-artifact@v5
uses: actions/upload-artifact@v6
if: failure()
with:
name: artifacts
Copy link

@cr-gpt cr-gpt bot Dec 12, 2025

Choose a reason for hiding this comment

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

Code Review:

  • This patch upgrades the action actions/upload-artifact from version 5 to version 6, which is a good practice to ensure you are using the latest features and improvements.
  • The condition if: failure() specifies that artifact uploading will only happen if the job has failed, which seems intentional based on the context.

Suggestions for improvement:

  • Consider adding a comment or descriptive text above or alongside the code to explain why the artifact upload happens only in case of failure. This can help future maintainers understand the intent behind this behavior.
  • Check the official release notes or documentation for changes between versions 5 and 6 of actions/upload-artifact to see if there are new features or considerations that you might want to leverage or be aware of.
  • Make sure tests cover this functionality to ensure it behaves as expected during failures.

Overall, the code patch seems like a reasonable update without any obvious bugs in the provided context.

Expand Down
Loading