Repository navigation
build(reactjs): update Raijin for workspace publishing - #164
Merged
Merged
Conversation
TorinAsakura
marked this pull request as ready for review
October 6, 2026 01:55
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Task
1.1.0and Yarn4.18.0for the shared workspace publisher. Align existing package sources with the current checks; let Raijin infer version decisions after mergeHow to test
Main scenario
CI=true yarn install --immutable --inline-buildsandyarn check --verify; expect immutable installation, formatting, lint, typecheck, unit and integration checks to passyarn workspaces foreach --since=origin/master -t --no-private run build; expect all nine changed public packages to buildyarn release version infer --dry-run; expectpatchfor each of the nine changed packages. Applying those decisions in a disposable run must update package versions and applicable workspace ranges through YarnAdditional scenario
.mjsRaijin bundles are absent and the checked-inyarn.jsmatches the released assetProof
yarn.jsmatches the Raijin1.1.0release asset SHA-25670cc9cd3583ffa73a2533911d6412517d7f52b3fd2bac860ea9b868d0319d89a@atls/code-runtimedependency and its sole ambient type reference; regenerated lock/PnP files contain no code-runtime. Raijin migrated the three legacy Git hooks while preserving their commands. Ordinaryyarn install --immutable --inline-buildsand a commit with active hooks passed.CI=true yarn install --immutable --inline-builds,yarn check --verify(10 unit tests and one integration test), and builds of all nine public workspaces passed locallypatchdecisions. A temporary Yarn version-apply dry-run showed the next versions:0.0.10, five0.1.1packages,0.2.1,1.0.4and0.1.48; the temporary decision file was removed so the shared workflow will infer after merge