Repository navigation
chore(upstream): sync upstream main through ea20e800 - #11
Merged
Merged
Conversation
Co-authored-by: Julius Marminge <[email protected]>
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.
Why
Upstream
t3codemoved ahead onmain, and this repo needs a controlled sync flow that keeps local divergences reviewable instead of landing directly onmain.What changed
mainthroughea20e800apps/desktop/scripts/electron-launcher.mjs0001to record the first upstream sync verificationValidation
bun installbun fmtbun lint(existing warnings-only baseline)bun typecheck