docs(changelog): version 1.12.0 [citest_skip]

[richm]

Update changelog and .README.html for version 1.12.0

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

Summary by Sourcery

Document the 1.12.0 release in project changelog.

New Features:

• Record role fingerprints in syslog in the changelog for version 1.12.0.

CI:

• Note CI updates including upgraded GitHub Actions, tox-lsr container test improvements and fixes, yum repo adjustments, and ansible-lint dependency handling in the changelog for version 1.12.0.

Documentation:

• Update CHANGELOG.md for the 1.12.0 release, including new features and CI/test-related changes.

Tests:

• Document test-related updates including support for ansible-test milestone version 2.22 in the changelog for version 1.12.0.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates documentation for the 1.12.0 release by adding a new changelog entry and regenerating the HTML README to reflect the new version and recent changes.

File-Level Changes

Change	Details	Files
Document the 1.12.0 release with its feature and CI-related updates in the changelog and associated HTML README.	Add a new [1.12.0] section to the changelog with release date List the new feature for role fingerprints in syslog under New Features Summarize CI, refactor, and testing-related updates under Other Changes Regenerate or update the HTML README to stay consistent with the new changelog entry	CHANGELOG.md .README.html

---

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 left some high level feedback:

• The list of CI-related changes mixes different capitalization and phrasing styles (e.g., ci: Comply... vs ci: ansible-lint requires...); consider making these consistent to improve readability of the changelog.
• There are two similar entries for Ansible partner certification compliance (refactor: comply... and ci: Comply...); it may be worth clarifying or merging them if they refer to the same underlying change to avoid confusion for readers.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The list of CI-related changes mixes different capitalization and phrasing styles (e.g., `ci: Comply...` vs `ci: ansible-lint requires...`); consider making these consistent to improve readability of the changelog.
- There are two similar entries for Ansible partner certification compliance (`refactor: comply...` and `ci: Comply...`); it may be worth clarifying or merging them if they refer to the same underlying change to avoid confusion for readers.

---

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.}