Skip to content

chore: sync public mirror from internal - #1251

Merged
evalops-mirror[bot] merged 1 commit into
mainfrom
sync/public-release-mirror
Sep 24, 2026
Merged

evalops-mirror[bot] merged 1 commit into
mainfrom
sync/public-release-mirror

Conversation

@evalops-mirror

Copy link
Copy Markdown
Contributor

Summary

  • sync the sanitized public tree from dx-corp/mono
  • keep dx-corp/code as a generated public mirror of the private source of truth
  • preserve public-owned CI and trusted-publishing workflows from the public checkout
  • internal source SHA: f3bd963e731ce726ed31d70a89894d983298a096
  • last generated public sync base: 293a5b94a296a4f7b16eba49923db04cbdba076a
  • previewed public-tree drift: 1 file(s) to copy/update and 0 stale file(s) to delete
  • public-only commits since last generated sync: 0
  • to pause generated syncs while hand-editing this branch, apply the sync-hold label to this PR; the sync workflow skips every push while it is set

Source-of-truth status

Projection: deixic-code

  • Source: dx-corp/mono@f3bd963e731ce726ed31d70a89894d983298a096

  • Prior destination base: 293a5b9

  • Content SHA-256: 29e7e643aca0e259d6bf6c423110fa84fe86a8dc49f33b85e0d4770228debcf1

  • Result: drift_detected; 1 changed, 0 deleted

  • Destination-owned content is preserved. Destination CI is a separate health signal.

  • copy/update .repository-projection.json

Drift sample

  • copy/update .repository-projection.json

Public-only commits since last generated sync

  • none detected since last generated sync

Validation

  • generated by the sync-public-release-mirror workflow in public-tree mode

Test Plan

  • generated by the maestro-sync-public-release-mirror workflow in public-tree mode
  • public-source-provenance require-internal-pr confirms internal source PR lineage
  • generated mirror PRs use the slim public CI path (fmt/clippy/smoke + provenance); full cargo test/evals already ran on internal main for this SHA
  • bot review threads on generated mirror PRs are advisory and do not block the next sync update

Staged Rollout

  • Staging is unnecessary for this generated mirror PR: it does not independently promote user-visible behavior. It mirrors already-reviewed internal source from dx-corp/mono@f3bd963e731ce726ed31d70a89894d983298a096, including existing hidden/evaluation surfaces, and keeps public package parity behind the established public-source-provenance gate.

@evalops-mirror
evalops-mirror Bot requested a review from a team as a code owner September 24, 2026 19:13
@evalops-mirror

Copy link
Copy Markdown
Contributor Author

Resolved 0 review-bot thread(s) on this generated public mirror PR.
Left 0 human-started thread(s) unresolved.

Review of mirrored code belongs on the mono source PR.
See https://github.com/dx-corp/mono/issues/9100 for the triage pattern.

@evalops-mirror
evalops-mirror Bot enabled auto-merge (squash) September 24, 2026 19:13
@evalops-mirror
evalops-mirror Bot merged commit 811c7a5 into main Sep 24, 2026
16 of 18 checks passed
@evalops-mirror
evalops-mirror Bot deleted the sync/public-release-mirror branch September 24, 2026 19:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants