Skip to content

build(deps): bump actions/upload-artifact from 4 to 5 #84

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

Merged
ykominami merged 2 commits into from
Dec 11, 2025
Merged

build(deps): bump actions/upload-artifact from 4 to 5 #84

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9813694
build(deps): bump actions/upload-artifact from 4 to 5
dependabot[bot] Oct 24, 2025
ad50f82
Merge branch 'master' into dependabot/github_actions/actions/upload-a…
ykominami Dec 11, 2025
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@v4
uses: actions/upload-artifact@v5
if: failure()
with:
name: artifacts
Copy link

@cr-gpt cr-gpt bot Oct 24, 2025

Choose a reason for hiding this comment

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

The code patch you provided looks like a minor change in the GitHub Actions workflow. Here is a brief code review:

  1. Bug Risk:

    • The change from v4 to v5 in the actions/upload-artifact may introduce potential risks if there are breaking changes or compatibility issues between those versions. It's important to check the release notes for v5 of actions/upload-artifact to ensure compatibility with your current workflow.

  2. Improvement Suggestions:

    • Consider incorporating more conditionals or checks to further refine when artifacts are uploaded. This can help optimize the workflow and prevent unnecessary artifact uploads.
    • Add more detailed comments describing what each step does, especially if the workflow becomes more complex.

Overall, if the upgrade from v4 to v5 doesn't pose any compatibility issues and the rest of your workflow is functioning as expected, this change seems relatively low-risk and should be straightforward to implement. Remember to test the updated workflow thoroughly after making this change.

Expand Down
Loading