Update changelog and CITATION.cff for v26.6.1.2#5606
Closed
aabills wants to merge 1 commit into
Closed
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #5606 +/- ##
==========================================
- Coverage 98.10% 98.10% -0.01%
==========================================
Files 339 339
Lines 31779 31805 +26
==========================================
+ Hits 31178 31201 +23
- Misses 601 604 +3 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
644441e to
a74d7e9
Compare
This was referenced Jun 16, 2026
Closed
Member
|
Superseded by #5618 |
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.
Changelog + CITATION update for the v26.6.1.2 patch release (RELEASE.md "Cutting a patch release", step 7).
The patch ships from
release/v26.6.1.2(branched offv26.6.1.1, cherry-picking the bug fixes only). This PR records the release onmain:# [Unreleased]into a dated# [v26.6.1.2]block.# [Unreleased]— it ships in the next feature release, not this patch.# [Unreleased]to the policy order (Breaking changes first; was a duplicated/out-of-orderBug fixes…Breaking changes…Bug fixes).CITATION.cffto26.6.1.2.Docs-only; no code changes. The release branch is tagged separately and is not merged to
main(avoids duplicate-hash commits per RELEASE.md).🤖 Generated with Claude Code