HYPERFLEET-761 - docs: add CHANGELOG.md

[rh-amarin]

Add CHANGELOG.md to align with project structure standard

Summary by CodeRabbit

• Documentation
  • Added comprehensive changelog documenting project release history with entries for new features, improvements, bug fixes, and security updates across releases.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign jsell-rh for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[coderabbitai]

Walkthrough

A new CHANGELOG.md file was added documenting the project's release history using the "Keep a Changelog" format with Semantic Versioning structure. The file includes an [Unreleased] section with placeholders for categorized entries (Added, Changed, Fixed, Security), multiple dated release entries across the main repository and associated plugins, and a detailed guidelines comment block describing expected content and formatting conventions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically identifies the main change: adding a CHANGELOG.md file following documentation best practices (Keep a Changelog format).
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 1-193: CHANGELOG.md documents multiple plugin and repository
releases but there are no corresponding git tags; create annotated (and signed
if you sign releases) git tags that exactly match the documented entries (e.g.,
hyperfleet-devtools-0.4.0, hyperfleet-jira-0.4.0, hyperfleet-code-review-0.2.0,
Repository-0.3.0, etc.), attach them to the appropriate commits reflecting each
release, and push the tags to origin so the repository history aligns with
CHANGELOG.md.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e11c4fcc-a235-439b-9277-c7fbb1694fa7

📥 Commits

Reviewing files that changed from the base of the PR and between 52e2619 and 1fe27cd.

📒 Files selected for processing (1)

• CHANGELOG.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify changelog versions match git tags

# List all version tags from the changelog
echo "Versions documented in CHANGELOG.md:"
rg -oP '(?<=\[)\d+\.\d+\.\d+(?=\])' CHANGELOG.md | sort -V | uniq

echo -e "\nGit tags in repository:"
git tag --list | grep -E '^v?[0-9]+\.[0-9]+\.[0-9]+' | sort -V

Repository: openshift-hyperfleet/hyperfleet-claude-plugins

Length of output: 193

---

Ensure git tags are created to match documented versions.

The CHANGELOG.md structure and format are excellent—it follows Keep a Changelog conventions with proper semantic versioning, clear categorization, reverse chronological ordering, and helpful maintainer guidelines.

However, verification shows the repository has no git tags while the changelog documents versions 0.1.0 through 0.4.0 across multiple plugins. Create corresponding git tags to align the repository's version history with the documented changelog entries. This ensures changelog accuracy and enables proper version tracking for releases.

🧰 Tools

🪛 LanguageTool

[style] ~79-~79: To elevate your writing, try using a synonym here.
Context: ...rendered as vertical bars making output hard to read; now using markdown code blocks...

(HARD_TO)

---

[uncategorized] ~79-~79: Did you mean the formatting language “Markdown” (= proper noun)?
Context: ...s making output hard to read; now using markdown code blocks for GitHub comments ## hyp...

(MARKDOWN_NNP)

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 1 - 193, CHANGELOG.md documents multiple plugin
and repository releases but there are no corresponding git tags; create
annotated (and signed if you sign releases) git tags that exactly match the
documented entries (e.g., hyperfleet-devtools-0.4.0, hyperfleet-jira-0.4.0,
hyperfleet-code-review-0.2.0, Repository-0.3.0, etc.), attach them to the
appropriate commits reflecting each release, and push the tags to origin so the
repository history aligns with CHANGELOG.md.