Skip to content

docs: Fix ISSUE-83's changelog entry landing under the wrong release - #105

Merged
exactml merged 1 commit into
masterfrom
docs/fix-changelog-entry-placement
Sep 20, 2026
Merged

exactml merged 1 commit into
masterfrom
docs/fix-changelog-entry-placement

Conversation

@exactml

@exactml exactml commented Sep 20, 2026

Copy link
Copy Markdown
Owner

PR #94's branch was rebased across four release cuts (v0.2.1 through v0.2.4) before merging, and the changelog entry it added silently rode along into the v0.2.1 section each time instead of staying under UNDER DEVELOPMENT -- #83 was never actually part of v0.2.1, it merged today. Moves the entry to where unreleased work belongs.

PR #94's branch was rebased across four release cuts (v0.2.1
through v0.2.4) before merging. Each rebase kept the entry
anchored to its neighboring text (right after ISSUE-82's entry),
which the release cuts had already moved out of UNDER DEVELOPMENT
and into the dated v0.2.1 section -- so the entry silently rode
along into a release it was never actually part of. #83 merged
today, after v0.2.4 was already published; moves the entry to
UNDER DEVELOPMENT where unreleased work belongs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@github-actions github-actions Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤖 marginal review

PR #105: docs: Fix ISSUE-83's changelog entry landing under the wrong release · open · 3a8a321eb10a90274bed555a01e243045565e549 → 57d5fc5db9d3581987f54fbade6720328f06d131 · 1 file changed

Changed files (1)
  • CHANGELOG.md

@exactml
exactml merged commit 3b5ffda into master Sep 20, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant