-
Notifications
You must be signed in to change notification settings - Fork 6
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
ci: Update to latest versions of all GH actions. #49
Conversation
WalkthroughThe pull request updates the GitHub Actions workflow configurations for linting, building, testing a Python package, and uploading packages to PyPI. Key changes include upgrading the versions of several actions: Changes
Possibly related PRs
Suggested reviewers
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (2)
🔇 Additional comments (7).github/workflows/release.yaml (3)
The upgrade from v3 to v4 brings performance improvements and Node 20 runtime. No breaking changes affect this workflow. ✅ Verification successfulLet me verify the GitHub Actions workflow files more thoroughly. The actions/checkout@v4 upgrade is safe to proceed The workflow files show standard usage of actions/checkout@v4 without any custom configurations that could be affected by the v3 to v4 upgrade. All instances use the default settings without fetch-depth or custom path parameters, making this a safe upgrade. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Verify no custom checkout path or fetch-depth configurations that might be affected
rg -l 'actions/checkout@v[0-9]' | xargs rg 'fetch-depth|path:'
Length of output: 2303 Script: #!/bin/bash
# Check all workflow files for checkout action configuration
fd -e yml -e yaml . .github/workflows/ -x cat {}
Length of output: 3136
The upgrade from v4 to v5 includes Node 20 runtime and improved caching mechanisms. The specified Python version "3.8" remains supported. ✅ Verification successfulThe upgrade to actions/setup-python@v5 is safe to proceed The verification shows that setup-python is used consistently across workflows with standard configuration patterns. No custom caching configurations are present that would be affected by v5's changes. The Python version specifications are straightforward, using either matrix variables or the explicit "3.8" version, which remains supported in v5. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Verify no custom cache configurations that might need adjustment
rg -l 'actions/setup-python@v[0-9]' | xargs rg 'cache:'
Length of output: 55 Script: #!/bin/bash
# Check all workflow files for setup-python usage and surrounding context
fd -e yml -e yaml -d 2 . .github/workflows/ -x rg -B 3 -A 3 'actions/setup-python@'
Length of output: 682
The upgrade from v3 to v4 includes Node 20 runtime and performance improvements. The artifact download configuration remains compatible. ✅ Verification successfulThe upgrade to actions/download-artifact@v4 is safe The workflow file shows standard usage of download-artifact with only the required 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Verify no custom merge-multiple or create-missing-directories configurations
rg -l 'actions/download-artifact@v[0-9]' | xargs rg 'merge-multiple|create-missing-directories:'
Length of output: 98 Script: #!/bin/bash
# Let's first check all occurrences of download-artifact to understand its usage
rg -A 3 'actions/download-artifact@v[0-9]'
Length of output: 44 Script: #!/bin/bash
# Let's check the workflow file directly to understand the download-artifact usage
cat .github/workflows/release.yaml
Length of output: 952 .github/workflows/package.yaml (4)
The upgrade to v4 is consistently applied across all jobs in the workflow. No job-specific configurations are affected. Also applies to: 49-49, 77-77
The upgrade to v5 is consistently applied across all jobs, maintaining compatibility with all specified Python versions (3.7, 3.8, 3.11). Also applies to: 51-53, 79-81 Line range hint The upgrade from v3 to v4 includes Node 20 runtime and performance improvements. The retention-days configuration remains supported. Line range hint The upgrade to v4 is consistently applied in both test jobs, maintaining the existing artifact download configurations. Also applies to: 84-87 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 using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For the PR title, how about:
ci: Update to latest versions of all GH actions.
References
Description
As indicated in the recent workflows, artifact action v3 has been deprecated: https://github.com/y-scope/clp-loglib-py/actions/runs/12093018591
This PR updates all GH action dependencies to the latest release:
Validation performed
Ensure the updated workflows passed.
Summary by CodeRabbit