Smithery is now a part of Arcade.dev! Read more in our announcement here
Rewrites changelog entries with cheeky, narrative flair following project conventions. Use this when asked to rewrite or update CHANGELOG.md entries.
Read CHANGELOG.md first and match its established voice. The file's own precedent beats
every rule below.
Never neutralize the voice — it is the deliverable.
## [X.Y.Z](compare-url) (YYYY-MM-DD) emoji
GitHub compare link and ISO date are mandatory. Emoji picked for this release — reach
for the obvious one only when nothing better fits. Repetition for emphasis (📡📡📡) is
allowed.
| Release | Body |
|---|---|
| Single-fix patch | Quote + one narrative paragraph. No bullets. |
| Multi-change | Quote + ### Highlights + closing paragraph |
| Any, with breaking changes | Add the Breaking Changes block before Highlights |
Opening quote is always italicized inside a blockquote, and carries the mood.
## [0.1.4](https://github.com/ChecKMarKDevTools/rai-lint/compare/v0.1.3...v0.1.4) (2026-01-14) 🧹
> _Because even the tiniest version bump deserves a drumroll, or at least a polite cough._
A quick patch to fix the commitlint package version that was apparently auditioning for a game of hide-and-seek. No user-facing changes, just the machinery getting its act together.
## [0.1.3](https://github.com/ChecKMarKDevTools/rai-lint/compare/v0.1.2...v0.1.3) (2026-01-08) 📡📡📡
> _A boring release, in the best possible way:_ this one is about making CI/release automation less fragile and keeping dependencies current.
No user-facing rule behavior changes in either package. If you linted commits yesterday, you're linting commits today — just with fewer ways for the release machinery to hurt itself.
### Highlights
- **Release automation is harder to derail.** Release Please configuration and "single-tag" wiring were fixed so tags/versions line up cleanly across this monorepo instead of drifting into "wait, which package did we publish?" territory.
- **Security + supply chain posture got a tune-up.** The security audit workflow was improved, and the `astral-sh/setup-uv` action was bumped so the Python toolchain setup stays aligned with the ecosystem.
Highlights = bold claim, then plain-language impact. Never a bare verb phrase.
State what broke · why · what the reader must do. Structure is identical across both tones; only the header changes.
**🚨 Breaking Changes (Yes, Really):** · **⚠️ The Part Where Things Break:****Breaking Changes (Shocking, I Know):** ·
**Things That Changed Because v0.x Means 'Surprise Mechanics':**Do:
Never:
* commit abc123).CHANGELOG.md content outside the section being rewritten.