Skip to content

fix: update deprecated GitHub Actions artifact actions to v4#7

Merged
ryoppippi merged 3 commits intomainfrom
fix/update-artifact-actions
May 27, 2025
Merged

fix: update deprecated GitHub Actions artifact actions to v4#7
ryoppippi merged 3 commits intomainfrom
fix/update-artifact-actions

Conversation

@ryoppippi
Copy link
Owner

Summary

  • Update actions/upload-artifact from v3 to v4
  • Update actions/download-artifact from v2 to v4

Motivation

GitHub deprecated v3 of the artifact actions on April 16, 2024. This was causing automatic failures in the CI pipeline with the error:

Error: This request has been automatically failed because it uses a deprecated version of `actions/upload-artifact: v3`. 
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/

Changes

Updated the GitHub Actions workflow file .github/workflows/ci.yaml:

  • Line 56: actions/upload-artifact@v3actions/upload-artifact@v4
  • Line 76: actions/download-artifact@v2actions/download-artifact@v4

Breaking Changes

None. The v4 versions of these actions maintain backward compatibility with the same input parameters.

Testing

The CI pipeline should run successfully after merging this PR. The artifact upload and download functionality will continue to work as expected.

References

🤖 Generated with Claude Code

ryoppippi and others added 3 commits May 27, 2025 13:53
Update actions/upload-artifact from v3 to v4 and actions/download-artifact
from v2 to v4 to address deprecation warnings. These actions were deprecated
on April 16, 2024 as per GitHub's announcement.

This ensures the CI pipeline continues to work properly and avoids automatic
failures due to deprecated action usage.

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @ryoppippi, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, gemini-code-assist here to provide a summary of this pull request. The primary intent of this PR, as stated in the title and description, is to address CI pipeline failures caused by the deprecation of older versions of GitHub Actions artifact actions. Specifically, it aims to update actions/upload-artifact from v3 to v4 and actions/download-artifact from v2 to v4 in the .github/workflows/ci.yaml file. While the description details these specific changes in ci.yaml, the provided patches also include the addition of a new CLAUDE.md file and an update to the clap dependency version in build.zig.zon. This summary covers the intended fix and the changes present in the provided patch content.

Highlights

  • CI Fix: Deprecated Actions: The main goal is to fix CI failures by updating the GitHub Actions upload-artifact and download-artifact steps to their latest v4 versions, as older versions were deprecated.
  • Dependency Update: The clap dependency in build.zig.zon has been updated from version 0.8.0 to 0.10.0.
  • New Documentation File: A new file, CLAUDE.md, has been added, providing guidance and context about the project for Claude Code.

Changelog

  • .github/workflows/ci.yaml
    • According to the PR description, this file was modified to update actions/upload-artifact from v3 to v4 (line 56) and actions/download-artifact from v2 to v4 (line 76). Note: The patch content for this file was not available in the provided context.
  • CLAUDE.md
    • Added a new file providing project overview, development commands, architecture, dependencies, and CI/CD information specifically for Claude Code.
  • build.zig.zon
    • Updated the clap dependency URL and hash to version 0.10.0 (lines 13-14).
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


CI pipeline breaks,
Old actions cause the failures,
Update brings green checks.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@ryoppippi ryoppippi merged commit ca1fa34 into main May 27, 2025
4 of 18 checks passed
@ryoppippi ryoppippi deleted the fix/update-artifact-actions branch May 27, 2025 13:05
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, titled 'fix: update deprecated GitHub Actions artifact actions to v4', aims to resolve issues with deprecated GitHub Actions. The PR description details changes to .github/workflows/ci.yaml.

However, the code patches provided for this review consist of:

  1. The addition of a new file, CLAUDE.md, which provides guidance for AI tools working with this repository.
  2. An update to the clap dependency from v0.8.0 to v0.10.0 in build.zig.zon.

The described changes to the GitHub Actions workflow files were not included in the diffs I reviewed. My feedback below pertains only to the CLAUDE.md and build.zig.zon changes.

The CLAUDE.md file is a thoughtful addition for AI-assisted development. It's also commendable that it includes a note (line 68) about an existing version mismatch in the project between build.zig and build.zig.zon.

There are a couple of points regarding the provided changes that would benefit from clarification before merging.

Summary of Findings

  • Discrepancy between PR Scope and Provided Changes: The PR is titled and described as a fix for deprecated GitHub Actions. However, the code patches reviewed here do not include changes to GitHub workflow files. Instead, they introduce CLAUDE.md and update the clap dependency. Please ensure all intended changes are included in the PR, or update the PR description to accurately reflect the current changes.
  • Undocumented Dependency Update / Scope Creep: The clap dependency was updated from v0.8.0 to v0.10.0 in build.zig.zon. This change is not mentioned in the PR description and seems unrelated to the PR's stated goal of updating GitHub Actions, making the PR's scope unclear.
  • Documentation Inconsistency: The newly added CLAUDE.md file (line 55) lists clap v0.8.0, which conflicts with the update to v0.10.0 in build.zig.zon (also part of this PR).
  • Minor Stylistic Issue (Not commented due to review settings): The new file CLAUDE.md is missing a final newline character. This is a low-severity issue and was not added as a specific comment due to review settings.

Merge Readiness

This PR, as presented in the provided diffs, introduces a new CLAUDE.md file and updates the clap dependency. The primary stated goal of updating GitHub Actions is not reflected in these changes.

Due to the undocumented scope change (the clap update) and the resulting documentation inconsistency in CLAUDE.md, I recommend addressing these points. It's also crucial to clarify whether the GitHub Actions updates are part of this PR or a separate effort.

As a reviewer, I cannot approve the pull request. Based on the current state of the reviewed patches, I suggest that the author address the identified issues, particularly the scope and documentation concerns, before this PR is considered for merging. If the GitHub Actions changes are indeed part of this PR, they should be included in the diff for review.


## Key Dependencies

- **clap v0.8.0**: Used for command-line argument parsing

Choose a reason for hiding this comment

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

medium

The clap dependency version mentioned here (v0.8.0) is inconsistent with the update in build.zig.zon to v0.10.0 (also part of this PR's changes). To maintain accuracy in this documentation, could you update this line to reflect the new version?

Suggested change
- **clap v0.8.0**: Used for command-line argument parsing
- **clap v0.10.0**: Used for command-line argument parsing

Comment on lines +13 to +14
.url = "https://github.com/Hejsil/zig-clap/archive/refs/tags/0.10.0.tar.gz",
.hash = "clap-0.10.0-oBajB434AQBDh-Ei3YtoKIRxZacVPF1iSwp3IX_ZB8f0",

Choose a reason for hiding this comment

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

medium

This update to the clap dependency (from v0.8.0 to v0.10.0) appears to be outside the stated scope of this PR, which is focused on GitHub Actions updates (as per the PR title and description).

Could you clarify if this change is intentionally part of this PR?

  • If so, it would be helpful to update the PR title and/or description to include this change for clarity and accurate tracking.
  • Otherwise, would it be better to move this dependency update to a separate PR to keep concerns separated and ensure this PR focuses solely on the GitHub Actions fix?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant