ci: update github actions dependencies #655
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
✅ Deploy Preview for reearth-web canceled.
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #655 +/- ##
==========================================
+ Coverage 22.87% 26.03% +3.16%
==========================================
Files 1570 1660 +90
Lines 167255 184361 +17106
Branches 2837 3900 +1063
==========================================
+ Hits 38255 47999 +9744
- Misses 127846 135273 +7427
+ Partials 1154 1089 -65
Flags with carried forward coverage won't be shown. Click here to find out more. |
renovate
bot
force-pushed
the
renovate/github-actions
branch
21 times, most recently
from
af9c816
to
cce76b9
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
6 times, most recently
from
ab216db
to
65582c8
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
8 times, most recently
from
54e6253
to
69023e0
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
10 times, most recently
from
8eeada5
to
13a5aa9
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
5 times, most recently
from
f1e64ce
to
8574eb4
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
2 times, most recently
from
10ccce8
to
989bc65
Compare
renovate
bot
force-pushed
the
renovate/github-actions
branch
from
989bc65
to
4d58981
Compare
WalkthroughThe recent updates across various GitHub Actions workflows primarily involve upgrading action versions to their latest releases. This enhances the CI/CD pipelines by introducing new features, improving performance, and ensuring better security. The actions updated include those related to checking out code, setting up environments, caching, uploading artifacts, and deploying applications, reflecting a commitment to maintaining modern and efficient workflows. Changes
Sequence Diagram(s)sequenceDiagram
participant User
participant CI/CD
participant Actions
participant AWS
participant GoogleCloud
User->>CI/CD: Trigger Workflow
CI/CD->>Actions: Checkout Code (v4)
Actions->>CI/CD: Code Checked Out
CI/CD->>Actions: Run Tests
Actions->>CI/CD: Tests Passed
CI/CD->>AWS: Deploy to AWS (v4)
CI/CD->>GoogleCloud: Deploy to GCP (v2)
AWS->>CI/CD: Deployment Successful
GoogleCloud->>CI/CD: Deployment Successful
CI/CD->>User: Notify Success
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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 as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
renovate
bot
force-pushed
the
renovate/github-actions
branch
from
4d58981
to
373f999
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range, codebase verification and nitpick comments (1)
.github/workflows/build_web.yml (1)
76-76: Breaking Changes Detected inactions/download-artifact@v4The release notes for version
v4.0.0indicate that there are breaking changes. Artifacts created with versionsv3and below are not compatible with thev4actions. Uploads and downloads must use the same major actions versions. Please review and update your workflows accordingly.
- Ensure that both upload and download steps in your workflows are using the same major version of the action.
- Review the release notes for any additional changes that may affect your workflow.
Analysis chain
Verify compatibility with
actions/download-artifact@v4.The
actions/download-artifactaction has been updated to versionv4. Ensure that there are no breaking changes affecting the artifact downloading process.Run the following script to check for any breaking changes in the release notes:
Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes in actions/download-artifact@v4 release notes. # Test: Search for breaking changes in the release notes. Expect: No breaking changes. gh release view actions/download-artifact --json body --jq '.body' | grep -i 'breaking changes'Length of output: 113
Script:
#!/bin/bash # Description: Verify the existence of the actions/download-artifact repository and list available releases. # Search for the repository URL for actions/download-artifact. gh repo view actions/download-artifact --json url --jq '.url' # List all releases for the actions/download-artifact repository, if it exists. gh release list --repo actions/download-artifactLength of output: 1137
Script:
#!/bin/bash # Description: Fetch release notes for actions/download-artifact@v4.0.0 and search for breaking changes. # Fetch the release notes for version v4.0.0. gh release view v4.0.0 --repo actions/download-artifact --json body --jq '.body' | grep -i 'breaking changes'Length of output: 425
Review details
Configuration used: .coderabbit.yaml
Review profile: CHILL
Files selected for processing (14)
- .github/workflows/build_server.yml (4 hunks)
- .github/workflows/build_web.yml (6 hunks)
- .github/workflows/ci.yml (3 hunks)
- .github/workflows/ci_docker_build_push.yml (2 hunks)
- .github/workflows/ci_server.yml (3 hunks)
- .github/workflows/ci_web.yml (2 hunks)
- .github/workflows/deploiy_aws.yml (1 hunks)
- .github/workflows/deploy_server_nightly.yml (1 hunks)
- .github/workflows/deploy_web_nightly.yml (1 hunks)
- .github/workflows/e2e.yml (2 hunks)
- .github/workflows/pr_title.yml (1 hunks)
- .github/workflows/release.yml (1 hunks)
- .github/workflows/renovate.yml (1 hunks)
- .github/workflows/reviewer_lottery.yml (1 hunks)
Files skipped from review due to trivial changes (2)
- .github/workflows/deploy_server_nightly.yml
- .github/workflows/reviewer_lottery.yml
Additional comments not posted (42)
.github/workflows/renovate.yml (1)
11-11: Verify compatibility withactions/checkout@v4.Ensure that the updated version of
actions/checkoutis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
actions/checkout@v4to confirm compatibility..github/workflows/pr_title.yml (2)
19-19: Verify compatibility withactions/labeler@v5.Ensure that the updated version of
actions/labeleris compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
actions/labeler@v5to confirm compatibility.
22-22: Verify compatibility withamannn/action-semantic-pull-request@v5.Ensure that the updated version of
amannn/action-semantic-pull-requestis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
amannn/action-semantic-pull-request@v5to confirm compatibility..github/workflows/deploy_web_nightly.yml (2)
16-16: Verify compatibility withgoogle-github-actions/auth@v2.Ensure that the updated version of
google-github-actions/authis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
google-github-actions/auth@v2to confirm compatibility.
20-20: Verify compatibility withgoogle-github-actions/setup-gcloud@v2.Ensure that the updated version of
google-github-actions/setup-gcloudis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
google-github-actions/setup-gcloud@v2to confirm compatibility..github/workflows/ci_web.yml (2)
19-19: Verify compatibility withactions/cache@v4.Ensure that the updated version of
actions/cacheis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
actions/cache@v4to confirm compatibility.
37-37: Verify compatibility withcodecov/codecov-action@v4.Ensure that the updated version of
codecov/codecov-actionis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
codecov/codecov-action@v4to confirm compatibility..github/workflows/deploiy_aws.yml (2)
24-24: Verify compatibility withaws-actions/configure-aws-credentials@v4.Ensure that the updated version of
aws-actions/configure-aws-credentialsis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
aws-actions/configure-aws-credentials@v4to confirm compatibility.
32-32: Verify compatibility withaws-actions/amazon-ecr-login@v2.Ensure that the updated version of
aws-actions/amazon-ecr-loginis compatible with the rest of the workflow and any specific features or configurations you rely on.Check the release notes for
aws-actions/amazon-ecr-login@v2to confirm compatibility..github/workflows/ci_server.yml (5)
13-13: Verify compatibility withactions/checkout@v4.Ensure that the new version of
actions/checkoutis compatible with your current workflow setup.Also applies to: 35-35
15-15: Verify compatibility withactions/setup-go@v5.Ensure that the new version of
actions/setup-gois compatible with your current Go setup and environment variables.Also applies to: 37-37
20-20: Verify compatibility withgolangci/golangci-lint-action@v6.Ensure that the new version of
golangci/golangci-lint-actionis compatible with your linting configuration.
30-30: Verify MongoDB version update.The MongoDB image has been updated from
5-focalto6-focal. Ensure that your application is compatible with MongoDB 6.
47-47: Verify compatibility withcodecov/codecov-action@v4.Ensure that the new version of
codecov/codecov-actionis compatible with your coverage report setup..github/workflows/release.yml (1)
43-43: Verify compatibility withactions/upload-artifact@v4.Ensure that the new version of
actions/upload-artifactis compatible with your artifact upload process..github/workflows/e2e.yml (4)
16-16: Verify compatibility withactions/setup-node@v4.Ensure that the new version of
actions/setup-nodeis compatible with your Node.js setup.
19-19: Verify compatibility withactions/checkout@v4.Ensure that the new version of
actions/checkoutis compatible with your current workflow setup.
23-23: Verify compatibility withactions/cache@v4.Ensure that the new version of
actions/cacheis compatible with your caching strategy.
48-48: Verify compatibility withactions/upload-artifact@v4.Ensure that the new version of
actions/upload-artifactis compatible with your artifact upload process..github/workflows/ci_docker_build_push.yml (5)
32-32: Verify compatibility withactions/checkout@v4.Ensure that the new version of
actions/checkoutis compatible with your current workflow setup.
34-34: Verify compatibility withdocker/setup-qemu-action@v3.Ensure that the new version of
docker/setup-qemu-actionis compatible with your QEMU setup.
36-36: Verify compatibility withdocker/setup-buildx-action@v3.Ensure that the new version of
docker/setup-buildx-actionis compatible with your Buildx setup.
38-38: Verify compatibility withdocker/login-action@v3.Ensure that the new version of
docker/login-actionis compatible with your Docker login process.
77-77: Verify compatibility withdocker/build-push-action@v6.Ensure that the new version of
docker/build-push-actionis compatible with your Docker build and push process..github/workflows/ci.yml (2)
13-13: Verify compatibility withactions/checkout@v4.Ensure that the new version of
actions/checkoutis compatible with your current workflow setup.Also applies to: 67-67
18-18: Verify compatibility withtj-actions/changed-files@v45.Ensure that the new version of
tj-actions/changed-filesis compatible with your file change detection process.Also applies to: 30-30
.github/workflows/build_server.yml (8)
100-100: Verify compatibility withdocker/setup-buildx-action@v3.The
docker/setup-buildx-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the Docker Buildx setup.Run the following script to check for any breaking changes in the release notes:
35-35: Verify compatibility withactions/setup-go@v5.The
actions/setup-goaction has been updated to versionv5. Ensure that there are no breaking changes affecting the Go setup.Run the following script to check for any breaking changes in the release notes:
Verification successful
No breaking changes found in
actions/setup-go@v5.The documentation confirms that there are no breaking changes for existing users, indicating that the update to version
v5is compatible with your setup.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes in actions/setup-go@v5 release notes. # Test: Search for breaking changes in the release notes. Expect: No breaking changes. gh release view actions/setup-go --json body --jq '.body' | grep -i 'breaking changes'Length of output: 104
Script:
#!/bin/bash # Description: List tags for actions/setup-go to verify the existence of version v5. # Test: List all tags for the actions/setup-go repository. gh repo view actions/setup-go --json nameWithOwner --jq '.nameWithOwner' | xargs -I {} gh api repos/{}/tagsLength of output: 12412
Script:
#!/bin/bash # Description: Search for changelog or documentation files in the actions/setup-go repository for breaking changes. # Test: Search for files that might contain breaking changes information. gh repo clone actions/setup-go temp-setup-go-repo cd temp-setup-go-repo grep -i 'breaking changes' -r .Length of output: 989
65-65: Verify compatibility withdawidd6/action-download-artifact@v6.The
dawidd6/action-download-artifacthas been updated to versionv6. Ensure that there are no breaking changes affecting the artifact downloading process.Run the following script to check for any breaking changes in the release notes:
Verification successful
No breaking changes found in
dawidd6/action-download-artifact@v6.The repository and version
v6exist, and no breaking changes were mentioned in the release notes. However, it is recommended to manually verify the workflow using this action to ensure compatibility.
- Ensure the workflow using
dawidd6/action-download-artifact@v6functions as expected.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes in dawidd6/action-download-artifact@v6 release notes. # Test: Search for breaking changes in the release notes. Expect: No breaking changes. gh release view dawidd6/action-download-artifact --json body --jq '.body' | grep -i 'breaking changes'Length of output: 120
Script:
#!/bin/bash # Verify the existence of the repository and list available releases. gh repo view dawidd6/action-download-artifact || echo "Repository not found" gh release list --repo dawidd6/action-download-artifact || echo "No releases found"Length of output: 6075
39-39: Verify compatibility withgoreleaser/goreleaser-action@v6.The
goreleaser/goreleaser-actionhas been updated to versionv6. Ensure that there are no breaking changes affecting the GoReleaser functionality.Run the following script to check for any breaking changes in the release notes:
Verification successful
No breaking changes found for
goreleaser/goreleaser-action@v6.The release notes for version
v6.0.0do not mention any breaking changes, indicating compatibility with the workflow. You can proceed with using this version.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes in goreleaser/goreleaser-action@v6 release notes. # Test: Search for breaking changes in the release notes. Expect: No breaking changes. gh release view goreleaser/goreleaser-action --json body --jq '.body' | grep -i 'breaking changes'Length of output: 116
Script:
#!/bin/bash # Description: List all available tags for goreleaser/goreleaser-action to verify the correct version. # List all tags for the repository gh repo view goreleaser/goreleaser-action --json tags --jq '.tags[].name' # List all releases for the repository gh release list --repo goreleaser/goreleaser-actionLength of output: 2337
Script:
#!/bin/bash # Description: Fetch release notes for goreleaser/goreleaser-action v6.0.0 and check for breaking changes. # Fetch release notes for v6.0.0 gh release view v6.0.0 --repo goreleaser/goreleaser-action --json body --jq '.body' | grep -i 'breaking changes'Length of output: 112
31-31: Verify compatibility withactions/checkout@v4.The
actions/checkoutaction has been updated to versionv4. Ensure that there are no breaking changes affecting the workflow.Run the following script to check for any breaking changes in the release notes:
Also applies to: 91-91
141-141: Verify compatibility withdocker/build-push-action@v6.The
docker/build-push-actionhas been updated to versionv6. Ensure that there are no breaking changes affecting the Docker image build and push process.Run the following script to check for any breaking changes in the release notes:
Verification successful
No breaking changes found in
docker/build-push-action@v6.The release notes for the latest version
v6.7.0of thedocker/build-push-actiondo not mention any breaking changes. The update should be compatible with the existing workflow.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Check for breaking changes in docker/build-push-action@v6 release notes. # Test: Search for breaking changes in the release notes. Expect: No breaking changes. gh release view docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'Length of output: 112
Script:
#!/bin/bash # Search for the correct repository for docker/build-push-action and verify versioning. # Find the repository for docker/build-push-action on GitHub Marketplace gh search repos "docker/build-push-action" --limit 1 --json nameWithOwner # Check if the version v6 exists in the repository gh release list --repo docker/build-push-action --limit 10Length of output: 882
Script:
#!/bin/bash # Retrieve release notes for docker/build-push-action v6 and check for breaking changes. # Fetch the release notes for the latest v6 version gh release view v6.7.0 --repo docker/build-push-action --json body --jq '.body' | grep -i 'breaking changes'Length of output: 108
98-98: Verify compatibility withdocker/setup-qemu-action@v3.The
docker/setup-qemu-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the QEMU setup.Run the following script to check for any breaking changes in the release notes:
102-102: Verify compatibility withdocker/login-action@v3.The
docker/login-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the DockerHub login process.Run the following script to check for any breaking changes in the release notes:
.github/workflows/build_web.yml (8)
111-111: Verify compatibility withactions/checkout@v4.The
actions/checkoutaction has been updated to versionv4. Ensure that there are no breaking changes affecting the workflow.
113-113: Verify compatibility withdocker/setup-qemu-action@v3.The
docker/setup-qemu-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the QEMU setup.
115-115: Verify compatibility withdocker/setup-buildx-action@v3.The
docker/setup-buildx-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the Docker Buildx setup.
117-117: Verify compatibility withdocker/login-action@v3.The
docker/login-actionhas been updated to versionv3. Ensure that there are no breaking changes affecting the DockerHub login process.
156-156: Verify compatibility withdocker/build-push-action@v6.The
docker/build-push-actionhas been updated to versionv6. Ensure that there are no breaking changes affecting the Docker image build and push process.
182-182: Verify compatibility withdawidd6/action-download-artifact@v6.The
dawidd6/action-download-artifacthas been updated to versionv6. Ensure that there are no breaking changes affecting the artifact downloading process.
44-44: Verify compatibility withactions/cache@v4.The
actions/cacheaction has been updated to versionv4. Ensure that there are no breaking changes affecting the caching process.Run the following script to check for any breaking changes in the release notes:
57-57: Verify compatibility withactions/upload-artifact@v4.The
actions/upload-artifactaction has been updated to versionv4. Ensure that there are no breaking changes affecting the artifact uploading process.Run the following script to check for any breaking changes in the release notes:
This PR contains the following updates:
v3->v4v3->v4v2->v4v2->v4v4->v5v4->v5v3->v4v3->v4v2->v4v1->v2v2->v4v2->v4v2->v6v2->v6v2->v3v2->v3v2->v3v3->v6v0->v2v0->v2v4->v65-focal->6-focalv36->v45Release Notes
actions/cache (actions/cache)
v4Compare Source
actions/checkout (actions/checkout)
v4Compare Source
actions/download-artifact (actions/download-artifact)
v4Compare Source
v3Compare Source
actions/labeler (actions/labeler)
v5Compare Source
actions/setup-go (actions/setup-go)
v5Compare Source
actions/setup-node (actions/setup-node)
v4Compare Source
actions/upload-artifact (actions/upload-artifact)
v4Compare Source
aws-actions/amazon-ecr-login (aws-actions/amazon-ecr-login)
v2Compare Source
See the changelog for details about the changes included in this release.
aws-actions/configure-aws-credentials (aws-actions/configure-aws-credentials)
v4Compare Source
This tag tracks the latest v4.x.x release
v3Compare Source
This tag tracks the latest v3.x.x release
codecov/codecov-action (codecov/codecov-action)
v4Compare Source
v3Compare Source
dawidd6/action-download-artifact (dawidd6/action-download-artifact)
v6Compare Source
Full Changelog: dawidd6/action-download-artifact@v5...v6
v5Compare Source
Full Changelog: dawidd6/action-download-artifact@v4...v5
v4Compare Source
What's Changed
New Contributors
Full Changelog: dawidd6/action-download-artifact@v3...v4
v3Compare Source
docker/build-push-action (docker/build-push-action)
v6Compare Source
v5Compare Source
v4Compare Source
v3Compare Source
docker/login-action (docker/login-action)
v3Compare Source
docker/setup-buildx-action (docker/setup-buildx-action)
v3Compare Source
docker/setup-qemu-action (docker/setup-qemu-action)
v3Compare Source
golangci/golangci-lint-action (golangci/golangci-lint-action)
v6Compare Source
v5Compare Source
v4Compare Source
google-github-actions/auth (google-github-actions/auth)
v2Compare Source
Floating v2 alias
v1Compare Source
Floating v1 alias
google-github-actions/setup-gcloud (google-github-actions/setup-gcloud)
v2Compare Source
Floating v2 alias
v1Compare Source
This is the floating v1 release.
goreleaser/goreleaser-action (goreleaser/goreleaser-action)
v6Compare Source
v5Compare Source
tj-actions/changed-files (tj-actions/changed-files)
v45Compare Source
Changes in v45.0.0
What's Changed
New Contributors
Full Changelog: tj-actions/changed-files@v44...v45.0.0
v44Compare Source
Changes in v44.5.7
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.7
Changes in v44.5.6
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.6
Changes in v44.5.5
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.5
Changes in v44.5.4
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.4
Changes in v44.5.3
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.3
Changes in v44.5.2
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.2
Changes in v44.5.1
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.1
Changes in v44.5.0
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.5.0
Changes in v44.4.0
What's Changed
fetch_depthfrom 50 to 25 and increasefetch_missing_history_max_retriesby @jackton1 in https://github.com/tj-actions/changed-files/pull/2060Full Changelog: tj-actions/changed-files@v44.3.0...v44.4.0
Changes in v44.3.0
What's Changed
Full Changelog: tj-actions/changed-files@v44.2.0...v44.3.0
Changes in v44.2.0
What's Changed
Full Changelog: tj-actions/changed-files@v44.1.0...v44.2.0
Changes in v44.1.0
What's Changed
Full Changelog: tj-actions/changed-files@v44.0.1...v44.1.0
Changes in v44.0.1
What's Changed
Full Changelog: tj-actions/changed-files@v44...v44.0.1
Changes in v44.0.0
🔥🔥 BREAKING CHANGE 🔥🔥
Overview
We've made a significant update to how pull requests (PRs) from forked repositories are processed. This improvement not only streamlines the handling of such PRs but also fixes a previously identified issue.
Before the Change
Previously, when you created a pull request from a forked repository, any files changed in the target branch after the PR creation would erroneously appear as part of the PR's changed files. This made it difficult to distinguish between the actual changes introduced by the PR and subsequent changes made directly to the target branch.
What Has Changed
With this update, a pull request from a fork will now only include the files that were explicitly changed in the fork. This ensures that the list of changed files in a PR accurately reflects the contributions from the fork, without being muddled by unrelated changes to the target branch.
What's Changed
Configuration
📅 Schedule: Branch creation - "before 3:00 am on the 4th day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.