add release notes

[Dert1129]

Summary by CodeRabbit

• Chores
  • Version 4.3 is now officially released.

[coderabbitai]

Walkthrough

The [Unreleased] tag is removed from the Release 4.3 header in the changelog, marking the release as finalized. The "Brief summary," "Breaking changes," and "Non-breaking changes" sections remain unchanged.

Changes

Cohort / File(s)	Summary
Documentation changelog.md	Removed [Unreleased] tag from Release 4.3 header to mark the release as finalized.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch KPMP-6635_release-notes

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 777f7400-0417-4734-b9de-3a49f2041d90

📥 Commits

Reviewing files that changed from the base of the PR and between 38eebc5 and 5a369e6.

📒 Files selected for processing (1)

• changelog.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Add an explicit release date to keep changelog headers consistent.

Line 3 now marks 4.3 as released (by removing [Unreleased]), but unlike prior entries it does not include a [Released <date>] suffix. Please add the release date for traceability.

Proposed change

-## Release 4.3 
+## Release 4.3 [Released 4/23/2026]

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	## Release 4.3
	## Release 4.3 [Released 4/23/2026]