ci: use python 3.11 to determine updated packages in PR description

[Czaki]

Summary by CodeRabbit

• Chores
  • Updated the script to compare package requirements against constraints_py3.11.txt instead of constraints_py3.9.txt.

[coderabbitai]

Walkthrough

This update modifies the script that checks for updated packages by changing the Git diff command to compare against a new constraints file, moving from "constraints_py3.9.txt" to "constraints_py3.11.txt". This adjustment ensures that the comparison is made with the package requirements for Python 3.11, aligning the script with newer dependencies.

Changes

Files	Change Summary
build_utils/check_updated_packages.py	Updated the Git diff command to compare against "constraints_py3.11.txt" instead of "constraints_py3.9.txt".

Poem

In the land of code, a script did shift,
From Python 3.9, it made a swift lift.
To 3.11, constraints now aligned,
Ensuring dependencies are well-defined.
A hop ahead, a rabbit's delight,
Keeping our packages always just right. 🐇

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

[sourcery-ai]

🧙 Sourcery has finished reviewing your pull request!

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sourcery-ai]

We've reviewed this pull request using the Sourcery rules engine. If you would also like our AI-powered code review then let us know.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 98af5f4 and c680005.

Files selected for processing (1)

• build_utils/check_updated_packages.py (1 hunks)

Additional comments not posted (1)

build_utils/check_updated_packages.py (1)

20-20: LGTM! But verify the correctness of the new file path.

The code changes are approved.

However, ensure that the new file path requirements/constraints_py3.11.txt is correct and exists in the repository.

Verification successful

---

File path verified and correct.

The new file path requirements/constraints_py3.11.txt exists in the repository. The code changes are correct and approved.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the existence of the new constraints file.

# Test: Check if the new constraints file exists. Expect: The file should exist.
if [ -f "requirements/constraints_py3.11.txt" ]; then
  echo "File exists."
else
  echo "File does not exist."
fi

Length of output: 83

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.05%. Comparing base (98af5f4) to head (c680005).
Report is 49 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1160      +/-   ##
===========================================
- Coverage    93.06%   93.05%   -0.02%     
===========================================
  Files          208      208              
  Lines        32763    32763              
===========================================
- Hits         30491    30486       -5     
- Misses        2272     2277       +5     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.