Is your feature request related to a problem? Please describe.
The repo has 30+ merged PRs (recent: #47, #32, #31, #26, #24, #23) and ships a
versioned API under /api/v1/..., but there is no CHANGELOG.md. Users
upgrading Lux, or clients depending on /api/v1/..., have no way to see what
changed between revisions without reading the git log.
Describe the solution you'd like
Add CHANGELOG.md at the repository root using the Keep a Changelog 1.1.0
format with Semantic Versioning:
- One
## [Unreleased] section.
- One
## [0.1.0] — 2026-06-06 section for the initial public release
(matches the repo's created_at).
- Backfill notable merged changes into
Added / Changed / Fixed under
Unreleased:
Describe alternatives you've considered
- Auto-generating via
release-drafter or git-cliff — rejected for the first
cut, since a hand-seeded file is faster to land and can be automated later.
- Relying on GitHub Releases only — rejected, because releases are empty and the
file works offline (the repo ships in a tarball / Docker image).
Additional context
CONTRIBUTING.md could gain a one-line "update CHANGELOG before merging"
note, but that is optional and out of scope for the first PR.- PR numbers in entries match the git log already on
main.
This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #51 either in the PR description or in a PR's comment.
🪙 Also, everyone can tip any user commenting /tip 20 @johnny603 (replace 20 with the amount, and @johnny603 with the user to tip).
📖 If you want to learn more, check out our documentation.
Is your feature request related to a problem? Please describe.
The repo has 30+ merged PRs (recent: #47, #32, #31, #26, #24, #23) and ships a
versioned API under
/api/v1/..., but there is noCHANGELOG.md. Usersupgrading Lux, or clients depending on
/api/v1/..., have no way to see whatchanged between revisions without reading the git log.
Describe the solution you'd like
Add
CHANGELOG.mdat the repository root using the Keep a Changelog 1.1.0format with Semantic Versioning:
## [Unreleased]section.## [0.1.0] — 2026-06-06section for the initial public release(matches the repo's
created_at).Added/Changed/FixedunderUnreleased:Added: pre-commit config (Add pre-commit configuration for code quality checks #26),scripts/ci.sh([WIP] Fix failing GitHub Actions job security #24), community healthfiles (Guard Snyk workflow against missing
SNYK_TOKEN#23), Snyk workflow guard (Guard Snyk workflow against missingSNYK_TOKEN#23).Changed: tightened Bandit scan scope,ruff >=0.16.5(Update ruff requirement from >=0.16.4 to >=0.16.5 #32),gunicorn >=26.2.0(Update gunicorn requirement from >=23.0.0 to >=26.2.0 #31).Fixed: Snyk job no longer fails whenSNYK_TOKENis unset.Describe alternatives you've considered
release-drafterorgit-cliff— rejected for the firstcut, since a hand-seeded file is faster to land and can be automated later.
file works offline (the repo ships in a tarball / Docker image).
Additional context
CONTRIBUTING.mdcould gain a one-line "update CHANGELOG before merging"note, but that is optional and out of scope for the first PR.
main.This repo is using Opire - what does it mean? 👇
💵 Everyone can add rewards for this issue commenting
/reward 100(replace100with the amount).🕵️♂️ If someone starts working on this issue to earn the rewards, they can comment
/tryto let everyone know!🙌 And when they open the PR, they can comment
/claim #51either in the PR description or in a PR's comment.🪙 Also, everyone can tip any user commenting
/tip 20 @johnny603(replace20with the amount, and@johnny603with the user to tip).📖 If you want to learn more, check out our documentation.