ci: update release-please.yml GitHub Actions versions

[dlaehnemann]

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions to the latest versions for improved workflow efficiency, including:
    • release-please-action upgraded to version v4.
    • checkout action upgraded to version v4.
    • setup-python action upgraded to version v5.
    • amannn/action-semantic-pull-request action upgraded to version v5.

[coderabbitai]

Walkthrough

The GitHub workflow files have been updated to use newer versions of actions. Specifically, the release-please-action has been upgraded from version v3 to v4, the checkout action has been updated from version v3 to v4, and the setup-python action has been upgraded from version v4 to v5. Additionally, the package-name parameter has been removed from the release-please-action configuration. Similar updates have been made in the CI workflow and the conventional PRs workflow, reflecting consistent version upgrades across the actions used.

Changes

File(s)	Change Summary
.github/.../release-please.yml	- Upgraded release-please-action from v3 to v4 (repository changed from GoogleCloudPlatform to googleapis) - Upgraded checkout action from v3 to v4 - Upgraded setup-python action from v4 to v5 - Removed the package-name parameter
.github/.../ci.yml	- Upgraded checkout action from v3 to v4 - Upgraded setup-python action from v4 to v5 (remains with python-version "3.11" and retains cache option)
.github/.../conventional-prs.yml	- Upgraded amannn/action-semantic-pull-request from v3.4.0 to v5

Poem

In the realm of code I hop with glee,
Upgrading actions as spryly as can be.
From v3 to v4 and v5 on parade,
Each update’s a hop in the progress I made.
Coding carrot dreams in a workflow ballet!

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between dcdbe07 and c89df2f.

📒 Files selected for processing (2)

• .github/workflows/ci.yml (6 hunks)
• .github/workflows/conventional-prs.yml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: testing

🔇 Additional comments (10)

.github/workflows/conventional-prs.yml (1)

14-14: Update to Semantic PR Action Version

The update from amannn/action-semantic-pull-request@v3.4.0 to v5 is correctly applied. Please verify that any behavioral or configuration changes in the new version do not affect our semantic pull request validations.

.github/workflows/ci.yml (9)

14-14: Updated Checkout Action in Formatting Job

The update to actions/checkout@v4 is appropriately applied in the formatting job, ensuring we benefit from the latest improvements.

---

16-18: Updated Setup-Python Action in Formatting Job

Upgrading to actions/setup-python@v5 in the formatting job is correct. Please double-check that the python-version parameter and any associated settings (if extended in the future) continue to perform as expected.

---

26-29: Enhanced Python Setup with Caching in Formatting Job

The subsequent use of actions/setup-python@v5 with the caching option for poetry dependencies is a valuable performance optimization.

---

41-43: Consistent Checkout Update in Linting Job

The linting job now also uses actions/checkout@v4, which aligns with our recent updates and ensures consistency across all jobs.

---

44-47: Updated Setup-Python in Linting Job

The change to actions/setup-python@v5 for the linting job is accurate. This step secures our linting environment with the latest Python setup improvements.

---

54-58: Caching Setup in Linting Job

Introducing the caching mechanism with the second actions/setup-python@v5 call in the linting job should reduce dependency installation times. This is a sound improvement.

---

77-77: Updated Checkout in Testing Job

The testing job’s checkout step now uses actions/checkout@v4, maintaining consistency with the other jobs.

---

81-84: Updated Setup-Python for Testing Environment

Upgrading to actions/setup-python@v5 within the testing job ensures that our test environment leverages the most recent Python configurations (with python-version: "3.11").

---

91-95: Improved Caching Configuration in Testing Job

The updated caching configuration in the testing job, via the second use of actions/setup-python@v5 with cache: poetry, is an efficient enhancement that should help speed up dependency installations.

---

🪧 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 generate docstrings to generate docstrings for this 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

.github/workflows/release-please.yml (1)

36-40: Redundant Setup-Python Usage with Caching
A second invocation of actions/setup-python@v5 is used here with caching enabled (cache: poetry). If both setups are required for distinct purposes (e.g., one for general environment setup and one for dependency caching), this is fine. Otherwise, consider consolidating them to simplify the workflow.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 61de847 and dcdbe07.

📒 Files selected for processing (1)

• .github/workflows/release-please.yml (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: testing

🔇 Additional comments (3)

.github/workflows/release-please.yml (3)

14-18: Release-please Action Version Upgrade
The action reference has been updated to use googleapis/release-please-action@v4. Please ensure that this new version’s configuration (including the removal of the package-name parameter) is compatible with your release process.

---

24-24: Checkout Action Version Upgrade
The workflow now uses actions/checkout@v4. Confirm that this upgrade meets your secure checkout and caching requirements for the job.

---

26-29: Setup-Python Action Update (First Invocation)
The actions/setup-python action has been upgraded to version v5 with python-version: "3.11". This update should bring performance enhancements and new features. Please verify that all subsequent steps work correctly with this environment.

[cmeesters]

test case