ci: Explicitly use ubunutu-22.04 to test wheels for Python3.7.

[LinZhihao-723]

Description

Reference: https://github.com/y-scope/clp-loglib-py/actions/runs/12837435781/job/35801116566?pr=51
ubuntu-latest has been upgraded to Ubuntu 24.04 which doesn't support Python 3.7. This PR changes Python 3.7's testing env from ubuntu-latest to ubuntu-22.04 explicitly to ensure the workflow can be successfully launched.

Validation performed

• Ensure all workflows passed.

Summary by CodeRabbit

• Chores
  • Updated GitHub Actions workflow configuration to use Ubuntu 22.04 for Python 3.7 testing environment.

[coderabbitai]

Walkthrough

The pull request introduces a modification to the GitHub Actions workflow configuration, specifically targeting the test-python37 job's operating system matrix. The change involves updating the runner environment from ubuntu-latest to the explicitly defined ubuntu-22.04, which provides a more precise and consistent testing environment for Python 3.7 tests.

Changes

File	Change Summary
.github/workflows/package.yaml	Updated test-python37 job to use ubuntu-22.04 instead of ubuntu-latest

The modification ensures a fixed Ubuntu version for test execution, potentially improving reproducibility and preventing unexpected variations caused by automatic updates to the latest Ubuntu runner.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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. (Beta)
• @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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/package.yaml (1)

45-47: Consider future-proofing the Python 3.7 testing strategy.

Given that Python 3.7 reached end-of-life on June 27, 2023, and you're already downloading Python 3.8 wheels for testing, it might be worth considering:

1. Adding a comment explaining why ubuntu-22.04 is specifically required
2. Creating a timeline for phasing out Python 3.7 support entirely

Add a comment above the matrix configuration:

    strategy:
      matrix:
+        # Using ubuntu-22.04 as it's the last LTS release supporting Python 3.7
        os: [macos-13, ubuntu-22.04]

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6c32c14 and 6632237.

📒 Files selected for processing (1)

• .github/workflows/package.yaml (1 hunks)

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

• GitHub Check: test (ubuntu-latest, 3.11)
• GitHub Check: test (ubuntu-latest, 3.8)
• GitHub Check: test-python37 (ubuntu-22.04, 3.7)
• GitHub Check: test-python37 (macos-13, 3.7)
• GitHub Check: test (macos-latest, 3.8)

🔇 Additional comments (1)

.github/workflows/package.yaml (1)

45-45: The change to use ubuntu-22.04 is appropriate and well-reasoned.

The explicit version specification for Ubuntu ensures consistent testing environment for Python 3.7, addressing the compatibility issue with Ubuntu 24.04. This is a necessary change as Python 3.7 is not supported in newer Ubuntu versions.