chore: sync main back into development after v1.13.0 - #482
Merged
Conversation
release: v1.13.0 — coverage bounds reach consumers, credential fixes reach the wheel
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
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.
Routine back-merge after the v1.13.0 release. Brings
main's merge commit (#480) ontodevelopmentso the two branches stop diverging by one commit per release.Merge as a MERGE COMMIT, never squash — squashing rewrites the release merge and reintroduces the divergence this exists to remove.
No content: every change was already on
developmentbefore promotion. This is the merge commit itself.Release verified end to end:
v1.13.0,git describev1.13.0, installed1.13.0, each read separately (C-343)🤖 Generated with Claude Code