Skip to content

cimas sync 2026-08-10 wave (3-week drift catch-up + standoc-models P3) - #450

Open
opoudjis wants to merge 1 commit into
mainfrom
cimas-sync-2026-08-10
Open

cimas sync 2026-08-10 wave (3-week drift catch-up + standoc-models P3)#450
opoudjis wants to merge 1 commit into
mainfrom
cimas-sync-2026-08-10

Conversation

@opoudjis

Copy link
Copy Markdown
Contributor

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:

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

  • Individual template design changes (those go through their own PRs into metanorma/ci first).
  • Wave-scale meta-issues (release scheduling, cadence): tracked via the metanorma/ci queue.

🤖

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants