docs(changelog): version 1.14.1 [citest skip]

[richm]

Update changelog and .README.html for version 1.14.1

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

Summary by Sourcery

Documentation:

• Add changelog entry for version 1.14.1, noting test behavior change around restoring services when final state is not found.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates documentation for the 1.14.1 release by adding a new changelog entry describing a test-related behavioral change.

File-Level Changes

Change	Details	Files
Add 1.14.1 release notes to the changelog documenting a test behavior change.	Add a new 1.14.1 section with date 2026-01-22 to the changelog Document an "Other Changes" entry describing that tests no longer restore the service if the final state is not-found, referencing PR test: do not restore service if final state not-found #286	CHANGELOG.md

---

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 found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `CHANGELOG.md:9` </location>
<code_context>
+
+### Other Changes
+
+- test: do not restore service if final state not-found (#286)
+
 [1.14.0] - 2026-01-20
</code_context>

<issue_to_address>
**suggestion (typo):** Consider rephrasing "final state not-found" for clearer grammar.

If this is prose rather than a literal state name, consider something like “do not restore service if the final state is not found” or dropping the hyphen. If `not-found` is a named state, consider quoting or otherwise marking it as such.

```suggestion
- test: do not restore service if the final state is not found (#286)
```
</issue_to_address>

---

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

[sourcery-ai]

suggestion (typo): Consider rephrasing "final state not-found" for clearer grammar.

If this is prose rather than a literal state name, consider something like “do not restore service if the final state is not found” or dropping the hyphen. If not-found is a named state, consider quoting or otherwise marking it as such.

Suggested change

	- test: do not restore service if final state not-found (#286)
	- test: do not restore service if the final state is not found (#286)