Skip to content
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.

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

build(deps): Bump actions/xxx-artifact from v3 to v4 #22468

Merged
merged 4 commits into from
Nov 7, 2024

Conversation

auricom
Copy link
Contributor

@auricom auricom commented Nov 7, 2024

Description

Closes: #22447

The breaking changes between v3 and v4 do not affect us as we did not use the mutable nature on artifacts.

https://github.com/actions/upload-artifact/blob/main/docs/MIGRATION.md

Forced the execution of download steps on this workflow execution : https://github.com/cosmos/cosmos-sdk/actions/runs/11723916073?pr=22468

The regression observed in 2023 does not seems to occur as of now.
#18752
#18751

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • New Features
    • Enhanced testing framework with additional library installation for improved compatibility.
  • Improvements
    • Updated GitHub Actions to the latest versions for better performance and functionality.
    • Artifact upload process refined for job failures, ensuring better tracking and retention.

Copy link
Contributor

coderabbitai bot commented Nov 7, 2024

📝 Walkthrough
📝 Walkthrough

Walkthrough

The pull request includes updates to the GitHub Actions workflows, specifically upgrading the versions of several actions used in the .github/workflows/test.yml and .github/workflows/v2-test.yml files. The actions/upload-artifact and actions/download-artifact actions have been updated from version v3 to v4. The actions/checkout and actions/setup-go actions have been set to versions v4 and v5, respectively. The overall structure and logic of the workflows remain unchanged.

Changes

File Change Summary
.github/workflows/test.yml Updated actions/upload-artifact and actions/download-artifact from v3 to v4; set actions/checkout to v4 and actions/setup-go to v5.
.github/workflows/v2-test.yml Updated actions/upload-artifact from v3 to v4 in test-system-v2 job; added step for installing musl library based on GIT_DIFF.

Assessment against linked issues

Objective Addressed Explanation
Upgrade upload-artifact action to v4 as per deprecation notice (#22447)

Possibly related PRs

  • ci: split system tests in two job #22080: The changes in this PR also involve the .github/workflows/test.yml file, specifically updating the actions/upload-artifact action from version v3 to v4, which is directly related to the version updates in the main PR.

Suggested reviewers

  • testinginprod

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@auricom auricom marked this pull request as ready for review November 7, 2024 13:31
Copy link
Member

@julienrbrt julienrbrt left a comment

Choose a reason for hiding this comment

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

cool! thanks

@julienrbrt
Copy link
Member

We probably need to do that to all version we maintain. I'll let dependabot do it for v0.52 as it is pretty similar.
However could you open a PR for v0.50 and v0.47?

@julienrbrt julienrbrt added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Nov 7, 2024
@auricom auricom added this pull request to the merge queue Nov 7, 2024
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
.github/workflows/test.yml (1)

77-77: Optimize the shell script by removing unnecessary cat.

Consider replacing the cat command with direct input redirection for better efficiency:

-          cat pkgs.txt.part.${{ matrix.part }} | xargs go test -mod=readonly -race -timeout 30m -coverprofile=${{ matrix.part }}profile.out -covermode=atomic -tags='ledger test_ledger_mock'
+          xargs go test -mod=readonly -race -timeout 30m -coverprofile=${{ matrix.part }}profile.out -covermode=atomic -tags='ledger test_ledger_mock' < pkgs.txt.part.${{ matrix.part }}
🧰 Tools
🪛 actionlint

77-77: shellcheck reported issue in this script: SC2002:style:1:5: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead

(shellcheck)

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e4b085b and 0380c62.

📒 Files selected for processing (1)
  • .github/workflows/test.yml (5 hunks)
🧰 Additional context used
🪛 actionlint
.github/workflows/test.yml

77-77: shellcheck reported issue in this script: SC2002:style:1:5: Useless cat. Consider 'cmd < file | ..' or 'cmd file | ..' instead

(shellcheck)

🔇 Additional comments (2)
.github/workflows/test.yml (2)

29-33: LGTM: Artifact action upgrades are properly implemented.

The upgrade of actions/upload-artifact and actions/download-artifact from v3 to v4 is:

  • Necessary due to v3 deprecation in December 2024
  • Safe as the breaking changes in v4 don't impact the current implementation
  • Consistently applied across all jobs

Also applies to: 37-41, 79-82, 110-113, 149-152, 170-190


Line range hint 1-1024: LGTM: Workflow structure is well-designed.

The workflow demonstrates good practices:

  • Clear job dependencies and organization
  • Efficient use of conditional execution
  • Comprehensive test coverage across modules

Merged via the queue into main with commit 4e24090 Nov 7, 2024
72 checks passed
@auricom auricom deleted the claude/github-actions branch November 7, 2024 15:44
mergify bot pushed a commit that referenced this pull request Nov 7, 2024
julienrbrt pushed a commit that referenced this pull request Nov 7, 2024
#22470)

Co-authored-by: auricom <27022259+auricom@users.noreply.github.com>
@coderabbitai coderabbitai bot mentioned this pull request Nov 8, 2024
12 tasks
alpe added a commit that referenced this pull request Nov 13, 2024
* main: (31 commits)
  docs: update links for https security protocol (#22514)
  build(deps): Bump github.com/bytedance/sonic from 1.12.3 to 1.12.4 in /log (#22513)
  feat(x/protocolpool)!: allow any coins in continuous funds (#21916)
  docs: Update protobuf  tx signing message format outer link (#22510)
  test(accounts): fix integration tests (#22418)
  chore(x): fix some typos in comment (#22508)
  build(deps): Bump cosmossdk.io/log from 1.4.1 to 1.5.0 (#22487)
  build(deps): Bump cosmossdk.io/core from 1.0.0-alpha.5 to 1.0.0-alpha.6 (#22502)
  build(deps): Bump golang.org/x/crypto from 0.28.0 to 0.29.0 (#22480)
  docs(adr75): server v2 (#21069)
  fix(server/v2): improve server stop (#22455)
  chore: prepare core changelog (#22495)
  refactor(store/v2): simplify genesis flow (#22435)
  build(deps): Bump google.golang.org/grpc from 1.67.1 to 1.68.0 (#22486)
  build(deps): Bump golang.org/x/sync from 0.8.0 to 0.9.0 (#22482)
  feat(x/circuit): Allow msg Reset with empty msgURL (#22459)
  build(deps): Bump actions/xxx-artifact from v3 to v4 (#22468)
  feat(stf/branch): simplify merged iterator (#22131)
  refactor(log): disable coloring in testing logger (#22466)
  chore(x/tx): update changelog to alpha.2 (#22465)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release Type: CI
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add github actions to the dependabot.yml
3 participants