ci: Ansible version must be string, not float [citest_skip]

[richm]

The ansible version is specified as a YAML floating point number. This causes
2.20 to be converted to 2.2 which breaks platforms that use ansible 2.20.
Ensure it and similar version numbers are specified in YAML as strings.

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

Summary by Sourcery

CI:

• Update GitHub Actions workflow matrix to define Ansible versions as strings instead of numeric values.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the GitHub Actions TFT workflow matrix to treat Ansible versions as strings instead of numeric values, preventing YAML from truncating version numbers like 2.20 to 2.2 and ensuring CI runs with the intended Ansible versions on various platforms.

Flow diagram for YAML Ansible version handling in CI

flowchart LR
  A[Define ansible_version in tft.yml matrix\nusing YAML string values] --> B[GitHub Actions loads workflow]
  B --> C[Matrix expands per platform\nwith ansible_version as string]
  C --> D[Runner job reads ansible_version\nwithout numeric truncation]
  D --> E[Correct Ansible version\n2.20, 2.19, 2.16, 2.17, 2.9 is installed]
  E --> F[CI tests run against intended\nAnsible versions on each platform]

Loading

File-Level Changes

Change	Details	Files
Represent Ansible versions as strings in the TFT GitHub Actions workflow matrix to avoid YAML float truncation.	Updated each matrix entry’s ansible_version value from an unquoted number to a quoted string (e.g., 2.20 → "2.20") for all listed platforms. Added an inline comment in the workflow to document that ansible_version must be a string to avoid YAML float conversion issues.	.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.}