Linux build: bump to Python 3.11.11

[jonathanperret]

Problem

python-appimage removed the 3.11.10 release from their repo.

Proposed solution

Like we did last time, we bump the version of Python used for the Linux build.

This is not satisfying but right now I don't have a better idea.

Summary by CodeRabbit

• New Features

  • Enhanced AppImage creation process with new steps for downloading, extracting, and installing dependencies.

• Improvements

  • Updated Python version for Linux builds to 3.11.11.
  • Standardized caching strategies across all build jobs for consistency.

• Documentation

  • Added comments to improve clarity and maintainability of the workflow.

[coderabbitai]

Walkthrough

The pull request modifies the GitHub Actions workflow in .github/workflows/build-multi-os.yml. It updates the Python version for Linux builds from 3.11.10 to 3.11.11 and enhances the AppImage creation process with new steps for downloading, extracting, and installing dependencies. The caching mechanism is improved with options to ensure workflow failure on cache miss and standardizes cache restoration across jobs. Similar caching strategies are applied to the build-windows and build-macos jobs, while maintaining the overall structure and clarity of the workflow.

Changes

File Path	Change Summary
.github/workflows/build-multi-os.yml	- Updated Python version in build-appimage job from 3.11.10 to 3.11.11.
	- Enhanced AppImage creation process with new steps for downloading, extracting, and installing dependencies.
	- Updated caching mechanism with enableCrossOsArchive: true and fail-on-cache-miss: true.
	- Standardized cache restoration steps across different jobs.
	- Applied similar caching strategies to build-windows and build-macos jobs.

Possibly related PRs

• Upgrade GitHub actions to current supported versions #705: This PR updates the GitHub Actions workflow in .github/workflows/build-multi-os.yml, which is directly related to the changes made in the main PR regarding the Python version and workflow enhancements.
• Fix Linux build after python-appimage release disappeared #722: This PR also modifies the .github/workflows/build-multi-os.yml file, specifically addressing Python version handling and ensuring compatibility with the python-appimage builds, which aligns with the changes in the main PR.

Suggested reviewers

• dl1com

---

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. (Experiment)
• @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 SonarQube Cloud

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)

.github/workflows/build-multi-os.yml (1)

443-444: Consider future alignment of Python versions across platforms.

While the current patch-level differences between platforms (3.11.9 for Windows/macOS vs 3.11.11 for Linux) should maintain compatibility, consider aligning these versions in a future update if possible. This would ensure consistent behavior across all platforms.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5b80726 and 683f3aa.

📒 Files selected for processing (1)

• .github/workflows/build-multi-os.yml (1 hunks)

🔇 Additional comments (1)

.github/workflows/build-multi-os.yml (1)

443-444: LGTM: Python version update is necessary and minimal.

The update from Python 3.11.10 to 3.11.11 for Linux builds is necessary due to the removal of 3.11.10 from the python-appimage repository. This patch-level version bump maintains compatibility while ensuring the build process continues to work.

[jonathanperret]

.github/workflows/build-multi-os.yml (1)> 443-444: Consider future alignment of Python versions across platforms.

While the current patch-level differences between platforms (3.11.9 for Windows/macOS vs 3.11.11 for Linux) should maintain compatibility, consider aligning these versions in a future update if possible. This would ensure consistent behavior across all platforms.

You're right bot, but I prefer minimizing the impact of this change for now. If 3.11.11 fails on Linux, it won't be worse than the current absence of a build. But if 3.11.11 breaks something on Mac or Windows, we'll have to fix it right away when we could have just stayed on a known working version.