Repository navigation
chore: sync main into development (promotion merge commit #1017) - #1026
Merged
Merged
Conversation
chore: promote development to main — wave-0 truth fixes, dependency floors, contributor intake and Dependabot
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.
What
Merges
mainintodevelopmentso the next promotion pull request (development→main) is not behindmain.maincarries one commit thatdevelopmentlacks: the merge commitde93cd7of the promotion #1017. It has no content of its own —git diff development HEADon this branch is empty.How to merge
Use Create a merge commit. Squashing would discard the merge commit this branch exists to bring in, and the next promotion would start behind
mainagain.🤖 Generated with Claude Code