Repository navigation
docs: reconstruct historical brand kit versions - #15
Conversation
coisa
added
the
changelog-maintenance
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 16 minutes. View limit details
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. Comment |
Changelog✅ Contribution check passed. Head: Base: Contribution: 0 new valid fragment(s). Policy: maintenance. |
Reconstruct the repository's missing history from commits reachable on main. There were no tags or GitHub Releases when inspected; these version numbers are retrospective proposals, not claims of publication at the original commit dates.
12a38b2f7f55e08e719269fba559c0bc9cbfdbb6ea130ec1af8c01e4b13d7767f7dc51ec216e3087e1c4dd7d9c25c61f36c8a93bea85ab241853b086Only
CHANGELOG.mdchanges. Both existing pending fragments remain byte-for-byte intact. The unmerged/closed shared-workflow branch is excluded.Validation with Fast Forward Changelog 0.3.0: pending-fragment check passes; format dry run is a no-op; the history floor is recognized as 0.2.0. With the two current patch fragments, the next plan is 0.2.1 (later contributions may change it).
Automatic version PR #13 is untouched: no edits, closure, merge or push to its branch. After this history is accepted on main, its normal workflow may recalculate the next version. This PR is explicit central-history maintenance and uses the maintainer-granted
changelog-maintenancelabel.GitHub synchronization: corresponding retrospective releases will be prepared as reviewable drafts at these exact commits. Public tags/releases wait for acceptance of the proposed mapping; draft creation does not consume fragments or change PR #13.
Prepared GitHub release drafts (visible to maintainers):
12a38b2f7f55e08e719269fba559c0bc9cbfdbb6ea130ec1af8c01e4b13d7767f7dc51ec216e3087e1c4dd7d9c25c61f36c8a93bea85ab241853b086Readback confirmed each draft target and exact maintained notes. No public tags were created. Merge this historical PR before the automatic version PR so the normal workflow can re-plan from the accepted baseline; do not manually rewrite that generated PR.