Repository navigation
chore: sync public mirror from internal - #1160
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Review the following changes in direct dependencies. Learn more about Socket 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
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.
Problem
The public Deixic Code tree is still at 0.10.90 while the merged Mono source is at 0.10.91. The scheduled
sync-public-release-mirrorjob for that merge is queued without a runner, leaving the reviewed public source and its session and disconnected-profile documentation behind.Summary
6878323651fdb771b8cbf76b08597b930938ce36with Mono's dedicated Code projection..repository-projection.jsonreceipt; delete no files.dx-corp/codemain.Internal source SHA:
6878323651fdb771b8cbf76b08597b930938ce36.Source-of-truth status
The committed Mono source and its existing sanitizer produced the same reviewed Code payload. The dedicated
project.mjsapply and verify commands report content digest325d36d4b27c054e6edd55e71460299cdf56f8dc3ed887ae92ac326b531e60bc, 80 copy/update paths, and zero deletions. The public version guard accepts 0.10.91 over 0.10.90. The source's official post-merge Maestro Clippy and full workspace test receipts passed on a clean tree identical to the merged source tree.Public-only commits since last generated sync
c50b5f57— finishdx-corp/codeownership migration (fix(release): finish dx-corp/code ownership migration #1150)4c484fec— remove obsolete browser packaging (fix(release): remove obsolete browser packaging #1159)Both remain in this branch's base. No destination-owned workflow or package-validation path changed.
Validation
node scripts/projections/project.mjs applyandverifyfordeixic-code— passed against this checkout.node products/maestro/scripts/check-prepared-public-mirror-tree.mjs --target <checkout>— passed.go run github.com/rhysd/actionlint/cmd/actionlint@v1.7.9 -shellcheck= -pyflakes=— passed on the prepared public tree.node --test scripts/version.test.mjs— 6 passed.node --test .github/workflows/check-release-workflow-contract.test.mjs— 84 passed;node .github/workflows/check-release-workflow-contract.mjspassed.node --test scripts/tag-release-contract.test.mjs— 3 passed;npm run check:workspace-contractandgit diff --checkpassed.npm run check:doc-pathsreports 15 dangling references, identically reproduced on untouched public main4c484fec; none are in changed documentation. It is a pre-existing finding, not a passing check.Full public Cargo build/test was not run on the local macOS checkout because its Homebrew
rustcis broken and only 13 GiB was free. Destination CI must validate the prepared public tree before merge; this PR does not publish an npm package or deploy a runtime.Test Plan
Inspect exact-head destination checks, resolve substantive review findings, then merge normally only after required contexts pass. This PR mirrors approved source; it does not claim a release.
Staged Rollout
No runtime or registry rollout occurs. The public repository receives the reviewed source projection; package publication remains a separate release action.
No-Issue: This is the scheduled source mirror of the merged Mono repository-family PR.