[codex] upgrade Next runtime dependencies#162
Draft
Che-Zhu wants to merge 1 commit into
Draft
Conversation
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.
Summary
pnpm-lock.yamlfor the updated dependency graph.useCallbackin the GitHub status/settings UI so effects have explicit stable dependencies.useId()so the terminal id is stable across client renders.Scope
This PR only includes the runtime dependency update and directly related React compatibility cleanup.
Generated
.qoder/repowikidocumentation files are intentionally excluded from this PR.Verification
pnpm lintexits 0. It currently reports 4 warnings fromreact-hooks/set-state-in-effect, including existing warning coverage in the import GitHub dialog and the settings/GitHub loading effects touched here.pnpm buildexits 0 with Next.js 16.2.6.pnpm testexits 0: 13 test files and 43 tests passed.