Conversation
promote: 타입 수정이 포함된 data를 main으로 올린다
perf(web): preserve home and marker identity with measured swipe caches
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…60927 sync: bring main ancestry into develop for protected promotion
This branch was successfully deployed
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.
Promote the tested rendering candidate from
developtodataafter #3056. Home provider readiness retains descendant state, Google markers reconcile by restaurant ID, swipe caches remain bounded, and initial admin loading commits consistently.Source-bound measurements and limitations are in
apps/web/performance/render-delivery-20260925/REPORT.md. The feature PR passed all 18 reported checks; local exact-dependency tests, lint, TypeScript parity, production build, and real Naver map desktop/mobile interaction passed. This promotion does not apply hosted database writes or claim production performance gains. Next step is the protecteddata → mainPR, then a SHA-bound production deployment with rollback readback.