Releases: anchildress1/rai-lint
Release list
gitlint-rai: v1.0.1
commitlint-plugin-rai: v1.0.1
gitlint-rai: v0.1.8
commitlint-plugin-rai: v0.1.8
commitlint-plugin-rai: v0.1.7
rai-lint v0.1.6
0.1.6 (2026-01-18) 🤖
Release Please has been gently informed what “initial” means.
Pinned Release Please’s initial version and enforced the single-tag scheme at the top level, so it stops trying to “bootstrap” a repo that already has tags and a manifest.
rai-lint v0.1.5
0.1.5 (2026-01-18) 🧯
A small patch with very little drama, which is exactly the point.
Docs got tweaked (again) to be more explicit about Signed-off-by guidance, and yes: I’m still trying to make the commitlint plugin install stop exploding under strict peer dependency enforcement. That’s the whole release. Aside: if Release Please changes its mind again and decides this release never happened, I cannot be held accountable; Git can take the stand.
rai-lint v0.1.4
0.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.
rai-lint v0.1.3
0.1.3 (2026-01-09) 📡📡📡
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-uvaction was bumped so the Python toolchain setup stays aligned with the ecosystem. - Paper cuts were removed. A couple of small-but-annoying config fixes landed (explicit PR pattern, missing Python version directive), and versions were normalized after an earlier mismatch.