chore: sync dev with main after the #430 promotion - #431
Merged
Merged
Conversation
Promote dev to main
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Back-merges the
dev→mainpromotion (#430) intodevso the two long-livedbranches stay identical.
After #430,
maincarries a merge commit (2c9977c) thatdevdoes not. ThisPR brings that commit into
dev— no file changes — sodevstays thesingle source of truth for ongoing work and the next
dev→maincomparisonstarts from a clean slate.
No code, configuration, or documentation changes. Not linked to an issue.
Testing: none required — zero diff. CI runs as a formality.