cimas sync 2026-08-10 wave (3-week drift catch-up + standoc-models P3) - #1
Merged
Merged
Conversation
Fortnightly cimas sync wave 2026-08-10. 97 of 137 mapped repos have accumulated drift over 3 weeks since last wave (2026-07-22). Key changes: standoc-models P3 monorepo entry (metanorma-core#16 / ci#390), mn-samples-plateau docker.yml unmap (ci#388), ci#375/#376 supersedes (ci#383/#384/#385), gh-actions/model/Makefile verify-images defensive check (ci#302/#303). request-checks: true
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
2 participants
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.
Fortnightly cimas sync wave 2026-08-10 (previous 2026-07-22, 3 weeks overdue).
Wave-scale context
97 of 137 mapped repos have accumulated drift. Key changes this wave:
metanorma-model-*entries collapsed into 1standoc-modelsentry.What to review on this repo
The branch diff shows what cimas synced from current templates. If any change is a clobbered opt-out (per-repo customization that shouldn't have been stripped), flag it and I'll unmap that file in cimas.yml — see the mn-samples-plateau#537 remediation pattern for the shape of the fix.
Non-scope
🤖