Make Drawing Board updates follow component publication - #48
raghubetina wants to merge 1 commit into
Conversation
Keep template pin updates and prebuild readiness downstream of component publication so the Codespaces fallback does not delay the local release. Update consumers when their requirements change and reuse relevant CI without rebuilding unchanged images.
|
Current audit coordination, 2026-09-26: approved Drawing Board #54 is being implemented in dockerfiles #7 and Drawing Board #59. Maintainer documentation moves from Drawing Board This relocation uses current-main guidance and does not absorb this PR's pending release-policy text. Preserve this PR's substantive scope and retarget its maintainer-document path after the destination lands. Do not merge an obsolete file location into the student template just to resolve conflicts. Service #762 and Drawing Board #48 remain related release-guidance work; neither is a prerequisite for the audit research or permission to publish a package/image. The orchestration root is sequencing the relocation pair first. |
|
Superseded by the maintainer-guidance relocation to firstdraft/dockerfiles and the released-tooling follow-up in #60. The coordinated release policy is already preserved in drawing-board/README.md at dockerfiles 4e0ac33f: update Drawing Board after service/package publication, run its container checks, and verify the merged prebuild without rebuilding an unchanged workspace image. Keeping this PR would restore deleted maintainer documentation to the student template. |
1 participant
Drawing Board tooling updates and prebuild refreshes now follow service, CLI, and Skill publication. They do not block publishing those components. Reuse the template change's relevant CI and rebuild the workspace image only when image inputs change; unchanged pins and setup need no refresh.
Validation: existing
script/checkand whitespace checks passed with pinned Ruby and Node. Tooling pins, runtime settings, image selection, and prebuild configuration are unchanged.