Skip to content

Conversation

@richm
Copy link
Contributor

@richm richm commented Feb 11, 2026

Add Fedora 43, remove Fedora 41 from Testing Farm CI

Signed-off-by: Rich Megginson [email protected]

Summary by Sourcery

Update Testing Farm CI workflow to test against current Fedora releases.

CI:

  • Replace Fedora 41 with Fedora 43 in the Testing Farm CI workflow matrix.
  • Adjust supported Fedora platforms in the workflow script to include Fedora 43 and drop Fedora 41, updating the associated Ansible version.

Add Fedora 43, remove Fedora 41 from Testing Farm CI

Signed-off-by: Rich Megginson <[email protected]>
@richm richm self-assigned this Feb 11, 2026
@sourcery-ai
Copy link

sourcery-ai bot commented Feb 11, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI to drop Fedora 41, add Fedora 43, and align the test matrix and supported platforms list (including Ansible versions) with current Fedora support.

Flow diagram for computing supported Fedora platforms in CI

flowchart TD
  A[Read meta_main meta/main.yml] --> B[Check if galaxy_tags contains fedora]
  B -->|yes| C[Add Fedora-42 to supported_platforms]
  C --> D[Add Fedora-43 to supported_platforms]
  B -->|no| E[Do not add generic Fedora platforms]

  A --> F[Check if galaxy_tags contains fedoraN pattern]
  F -->|yes| G[Add specific Fedora versions to supported_platforms]
  F -->|no| H[No specific Fedora versions added]
Loading

File-Level Changes

Change Details Files
Update Testing Farm supported platforms and matrix from Fedora 41 to Fedora 43, including Ansible version alignment.
  • Adjust the dynamic supported_platforms construction so Fedora 43 is added alongside Fedora 42 while Fedora 41 is no longer appended.
  • Update the Testing Farm job matrix to remove Fedora 41 and its Ansible 2.17 entry.
  • Add a Fedora 43 matrix entry with Ansible 2.20, keeping Fedora 42 mapped to Ansible 2.19 and leaving other platforms unchanged.
.github/workflows/tft.yml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey - I've left some high level feedback:

  • Consider centralizing the Fedora versions and corresponding Ansible versions (used both in supported_platforms construction and the matrix) into a single variable or mapping to avoid duplication and reduce the chance of inconsistencies in future updates.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider centralizing the Fedora versions and corresponding Ansible versions (used both in `supported_platforms` construction and the matrix) into a single variable or mapping to avoid duplication and reduce the chance of inconsistencies in future updates.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@richm richm merged commit 8d03c21 into main Feb 11, 2026
27 of 29 checks passed
@richm richm deleted the f43 branch February 11, 2026 19:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant