chore: use PyQt6 in pre-tests

[Czaki]

Summary by Sourcery

Update the CI workflow to switch the backend from PyQt5 to PyQt6 for pre-tests.

CI:

• Update the CI workflow to use PyQt6 instead of PyQt5 for pre-tests.

Summary by CodeRabbit

• Chores
  • Updated the backend framework from PyQt5 to PyQt6 in the testing workflow configuration.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the pre-release testing workflow to use PyQt6 instead of PyQt5 as the backend for testing.

File-Level Changes

Change	Details	Files
Switched the backend from PyQt5 to PyQt6 in the pre-release testing workflow	Updated the BACKEND environment variable from PyQt5 to PyQt6	.github/workflows/test_prereleases.yml

---

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.

[coderabbitai]

Walkthrough

The pull request modifies a GitHub Actions workflow file by updating the environment variable BACKEND from PyQt5 to PyQt6. This change reflects an update in the backend framework used for testing, potentially impacting the interaction with graphical user interface components.

Changes

Files	Change Summary
.github/workflows/test_prereleases.yml	Updated BACKEND variable from PyQt5 to PyQt6

Poem

In the garden where code does play,
A bunny hops with joy today.
PyQt5 has taken its leave,
PyQt6 now weaves a new weave.
With every change, we dance and cheer,
For brighter tests are drawing near! 🐇✨

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 6ee3209 and 4cd8400.

Files selected for processing (1)

• .github/workflows/test_prereleases.yml (1 hunks)

Additional comments not posted (1)

.github/workflows/test_prereleases.yml (1)

87-87: Verify compatibility and test results with PyQt6.

The change looks good! Updating the BACKEND environment variable from PyQt5 to PyQt6 indicates a shift in the backend framework for the job.

Please ensure that:

1. The PyQt6 version is compatible with the other dependencies and the application code.
2. The tests still pass and provide the expected coverage with PyQt6.

You can run the following commands to verify the compatibility and test results:

Verification successful

---

Change to PyQt6 appears safe and well-prepared

The codebase analysis reveals that the project is already set up to handle both PyQt5 and PyQt6:

1. The tox.ini file includes test configurations for both PyQt5 and PyQt6, indicating existing cross-version compatibility.
2. No direct PyQt5-specific imports or usage were found that would break with PyQt6.
3. A previous changelog entry mentions updating the test environment to not use PyQt5, aligning with this change.

Given these observations, the change to PyQt6 is likely safe. However, to ensure everything works as expected:

• Run the test suite with the new PyQt6 configuration.
• Pay attention to any subtle differences in behavior between PyQt5 and PyQt6.

Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash

# Verify PyQt6 compatibility
pip check

# Run tests with PyQt6
python -m tox run -v -- -v

Length of output: 185

---

Script:

#!/bin/bash

# Search for PyQt imports in the codebase
echo "PyQt imports:"
rg "from PyQt\d? import" -n

# Look for mentions of PyQt versions in configuration files
echo -e "\nPyQt versions in configuration files:"
rg "PyQt\d" -g "*.{yml,yaml,ini,cfg,conf}" -n

# Check for PyQt version mentions in documentation files
echo -e "\nPyQt versions in documentation:"
rg "PyQt\d" -g "*.{md,rst,txt}" -n

# Search for any PyQt-related comments
echo -e "\nPyQt-related comments:"
rg "#.*PyQt" -n

Length of output: 1270

---

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 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.

[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

[sourcery-ai]

Hey @Czaki - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}