Repository navigation
docs: issues fixed on unreleased v3 close on merge - #585
Merged
Merged
Conversation
CONTRIBUTING.md said a fix merged only to v3 does not close its issue. The policy since 2026-10-06 is narrower: only fixes that ship in a patch to a published line (v2.0.x) stay open until that release; fixes on a branch with no release yet close on merge and stay listed in #421 when a published release has the bug. CLAUDE.md and DURABILITY.md follow. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U611mBGbkSqJeSwNz2xd7s
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01U611mBGbkSqJeSwNz2xd7s
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This was referenced Oct 14, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
CONTRIBUTING.mdsaid a fix merged only tov3does not close its issue. That contradicts the policy decided on 2026-10-06 and re-confirmed today: only issues fixed in a patch to a published line (v2.0.x) stay open until that release is out. Issues fixed on a branch with no release yet (v3before v3.0.0) close on merge, and stay listed in #421 when a published release has the bug.CONTRIBUTING.md: the known-issues rule, split into the two cases.CLAUDE.md: the same, plus a note that closing keywords do not fire onv3(not the default branch), so those issues are closed withgh issue close.docs/DURABILITY.md: the sentence about when labelled issues close.Left as they are:
ROADMAP.mdandCHANGELOG.mddescribe what shipped in v2.0.2 (#399), andPHILOSOPHY.mdonly says these bugs stay visible, which #421 still does.The docs site reads
CHANGELOG.mdand the error reference from this repo and has no copy of this text, so it needs no change.🤖 Generated with Claude Code
https://claude.ai/code/session_01U611mBGbkSqJeSwNz2xd7s