ci: Add Fedora 43, remove Fedora 41 from Testing Farm CI

[richm]

Add Fedora 43, remove Fedora 41 from Testing Farm CI

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

Update Testing Farm CI to drop Fedora 41 and add Fedora 43 coverage.

CI:

• Remove Fedora 41 from the Testing Farm GitHub Actions matrix and supported platforms detection.
• Add Fedora 43 with the appropriate Ansible version to the Testing Farm GitHub Actions matrix and supported platforms detection.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI to drop Fedora 41 and add Fedora 43, including adjusting the supported platforms detection and the test matrix with appropriate Ansible versions.

Flow diagram for updated supported_platforms detection in tft workflow

flowchart TD
  A[Read_meta_main_yml] --> B[Check_galaxy_tags_for_fedora]
  B -->|matches_fedora| C[Append_Fedora_42_to_supported_platforms]
  C --> D[Append_Fedora_43_to_supported_platforms]
  B -->|no_match| E[Skip_generic_Fedora_platforms]

  D --> F[Check_galaxy_tags_for_specific_fedora_versions]
  E --> F

  F --> G[Continue_with_Testing_Farm_matrix]

Loading

File-Level Changes

Change	Details	Files
Update supported Fedora versions detected for Testing Farm CI runs.	Remove Fedora 41 from the dynamically constructed supported_platforms list. Ensure Fedora 42 remains in supported_platforms. Add Fedora 43 to the supported_platforms list when Fedora is tagged in galaxy_info.	.github/workflows/tft.yml
Adjust Testing Farm CI job matrix to test on Fedora 42 and Fedora 43 with current Ansible versions.	Remove the Fedora 41 / Ansible 2.17 matrix entry. Keep Fedora 42 but bump it to run with Ansible 2.19. Add a Fedora 43 entry running with Ansible 2.20. Retain existing CentOS-related matrix entries 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

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

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

---

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 and I'll use the feedback to improve your reviews.}