docs: add CHANGELOG (baseline 0.2.0)#21
Merged
Merged
Conversation
The repo had no CHANGELOG, no tags, and no way to pin or cite a build, which the GLM review flagged. pyproject already declares version 0.2.0, so the baseline entry documents the shipped public-alpha feature set at 0.2.0 rather than the 0.1.0 the review assumed. Unreleased holds the approval-binding and constant-time auth fixes now in flight. No em-dashes, per the public-copy convention. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The repo had no CHANGELOG, no tags, and no way to pin or cite a build. The GLM review flagged this ("Public alpha with zero GitHub releases makes it impossible to pin or cite a build").
Note on the version
The review assumed
v0.1.0-alpha, butapps/orchestrator/pyproject.tomlalready declaresversion = "0.2.0". Cutting a 0.1.0 tag would be a regression, so the baseline entry is [0.2.0], matching the package metadata. Alpha status is carried by the README badge and the changelog preamble, not a PEP 440 suffix, which is the common 0.x convention.Contents
Keep a Changelog format, no em-dashes per the public-copy convention.
Not done here (needs your call)
Cutting the actual
v0.2.0git tag and GitHub release is a publish action, and it depends on whether you want #19 and #20 in 0.2.0 first. My recommendation: merge #19 and #20, move those two items from Unreleased into [0.2.0], then tagv0.2.0from master. I can prepare the exact commands on your go.