Skip to content

add fedora43, remove fedora40#5329

Merged
renecannao merged 4 commits into
v3.0from
v3.0.6-add_fedora43
Feb 3, 2026
Merged

add fedora43, remove fedora40#5329
renecannao merged 4 commits into
v3.0from
v3.0.6-add_fedora43

Conversation

@mirostauder

@mirostauder mirostauder commented Jan 27, 2026

Copy link
Copy Markdown
Contributor

add new package builds for fedora43
remove old fedora40

Summary by CodeRabbit

  • Chores
    • Updated build infrastructure to add Fedora 42 and Fedora 43 for amd64 and arm64.
    • Removed Fedora 40 and Fedora 41 build targets.
    • Aligned CI/service definitions and image tags to reflect Fedora 42→43 migration.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @mirostauder, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request systematically updates the project's build environment to incorporate the latest Fedora release, Fedora 43, while simultaneously phasing out support for the older Fedora 40. The changes ensure that the build process remains current with operating system advancements, affecting both amd64 and arm64 build targets and their respective Docker Compose service definitions.

Highlights

  • Fedora 43 Support Added: New package build configurations for Fedora 43 have been introduced for both amd64 and arm64 architectures, including standard, clang, and debug variants.
  • Fedora 40 Support Removed: All package build configurations and associated Docker Compose services for Fedora 40 have been deprecated and removed.
  • Build System Updates: The Makefile and docker-compose.yml files were updated to reflect the addition of Fedora 43 and the removal of Fedora 40 from the build matrix.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@coderabbitai

coderabbitai Bot commented Jan 27, 2026

Copy link
Copy Markdown

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

Fedora version entries were advanced: packaging lists in the Makefile now include fedora42 and fedora43 (replacing older fedora40/41/42 variants for amd64 and arm64). docker-compose services for Fedora builds were renamed/updated (removed fedora40 group, migrated fedora41→fedora42→fedora43) with image tag and PKG_RELEASE updates.

Changes

Cohort / File(s) Summary
Makefile
Makefile
Replaced Fedora packaging targets: removed older fedora40/41/42 variants and added fedora42, fedora42-clang, fedora42-dbg, plus fedora43, fedora43-clang, fedora43-dbg entries for amd64 and arm64.
Docker Compose — Fedora build services
docker-compose.yml
Removed fedora40_* build services. Renamed/migrated fedora41_*fedora42_* and then fedora42_*fedora43_*; updated service keys, image tags (e.g., build-fedora42-v3.0.3build-fedora43-v3.0.6), and PKG_RELEASE values (fedora42→fedora43 and corresponding -clang/-dbg variants). Preserved build-type envs like PROXYSQL_BUILD_TYPE=clickhouse.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 I hopped through trees of config and tag,
Swapped forty for forty-two, then pushed to forty‑three — a wag!
Images renamed, releases aligned with glee,
Docker and Makefile dance — a tidy spree. 🥕

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly and accurately summarizes the primary changes: adding Fedora 43 and removing Fedora 40 package builds across the modified files.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch v3.0.6-add_fedora43

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request correctly updates the build configuration to add support for Fedora 43 and remove Fedora 40. The changes in the Makefile and the removal of Fedora 40 services from docker-compose.yml are appropriate. However, I've noticed an inconsistency in the Docker image tags used for the new Fedora 43 build services, which should be addressed to ensure consistency and prevent potential build issues.

Comment thread docker-compose.yml
fedora43_build:
extends:
service: _build
image: proxysql/packaging:build-fedora43-v3.0.6

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The Docker image tag uses version v3.0.6, which is inconsistent with all other build services in this file that use v3.0.3. To maintain consistency across build environments and prevent potential build failures if the image doesn't exist, it's recommended to use v3.0.3.

    image: proxysql/packaging:build-fedora43-v3.0.3

Comment thread docker-compose.yml
fedora43_clang_build:
extends:
service: fedora43_build
image: proxysql/packaging:build-clang-fedora43-v3.0.6

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The Docker image tag uses version v3.0.6, which is inconsistent with all other build services in this file that use v3.0.3. To maintain consistency across build environments, it's recommended to use v3.0.3 here as well.

    image: proxysql/packaging:build-clang-fedora43-v3.0.3

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the build infrastructure to support Fedora 43 while removing support for the older Fedora 40. The changes ensure that package builds are maintained for currently supported Fedora versions (41, 42, and 43) across both amd64 and arm64 architectures.

Changes:

  • Removed Fedora 40 build service definitions from docker-compose.yml
  • Added Fedora 43 build service definitions (standard, clang, and debug variants) to docker-compose.yml
  • Updated Makefile targets to replace fedora40 with fedora43 for both amd64 and arm64 package builds

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
docker-compose.yml Removed fedora40_build, fedora40_clang_build, and fedora40_dbg_build services; added fedora43_build, fedora43_clang_build, and fedora43_dbg_build services using v3.0.6 build images
Makefile Updated amd64-fedora and arm64-fedora targets to include fedora43 and exclude fedora40

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@renecannao

Copy link
Copy Markdown
Contributor

Fedora 41 is already EOL , I don't think we should add it

@renecannao

Copy link
Copy Markdown
Contributor

@copilot : remove also support for Fedora 41

Copilot AI commented Feb 3, 2026

Copy link
Copy Markdown
Contributor

@renecannao I've opened a new pull request, #5338, to work on those changes. Once the pull request is ready, I'll request review from you.

Copilot AI and others added 2 commits February 3, 2026 13:47
Co-authored-by: renecannao <3645227+renecannao@users.noreply.github.com>
Remove Fedora 40 and 41 support, add Fedora 43
@renecannao
renecannao merged commit 69ea21e into v3.0 Feb 3, 2026
3 of 4 checks passed
@sonarqubecloud

sonarqubecloud Bot commented Feb 3, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants