ai/mission-control
Watch
1
0
Fork
You've already forked mission-control
 0
Code Issues 4 Pull requests 7 Projects Releases 91 Packages 2 Wiki Activity

fix(ci): isolate deployment tooling dependencies #44

Merged
morten-olsen merged 1 commit from fix/deployment-tool-install into main 2026-10-08 19:17:09 +02:00
Conversation 1 Commits 1 Files changed 6 +71 -2
paperclip commented 2026-10-08 19:08:29 +02:00
Contributor

Merged main deploy-access pipeline208 exited137 during full-workspace pnpm install, before any access assertion. Its512Mi budget is appropriate for a small deployment tool; the scripts require only yaml externally. Termination reason was not retained, so OOM remains a hypothesis.

Install a standalone scripts project with exact yaml2.9.1, frozen integrity-pinned lockfile and existing pnpm10.28.0. Both release:deploy-access and release:deploy use that install with DEPLOY_TOKEN removed. Keep runner pins, resource bounds and main/tag secret gates. A no-secret cold-install workflow imports the actual CLI in the same pinned runner and512Mi budget; no deployment or forge contact occurs.

Validation:25 deployment/concurrency/workflow tests pass, ESLint scripts passes,60 workflow event renderings and strict Woodpecker lint pass. Local single-package frozen install and CLI import pass. task is unavailable locally; actual Task entry point and resource-bounded cold run are required in CI. Owner will wait for green PR pipeline before validator review and for trusted-main deploy-access success after merge before the approved receipt release.

Rollback: revert this commit; it changes tooling installation only and makes no GitOps or database mutation. Receipt rollback artifact and Morten's migration/release approval are retained on parent22d19043. Production remains0.13.0. DevOps/Security reviews required before merge.

Merged main deploy-access pipeline208 exited137 during full-workspace pnpm install, before any access assertion. Its512Mi budget is appropriate for a small deployment tool; the scripts require only yaml externally. Termination reason was not retained, so OOM remains a hypothesis. Install a standalone scripts project with exact yaml2.9.1, frozen integrity-pinned lockfile and existing pnpm10.28.0. Both release:deploy-access and release:deploy use that install with DEPLOY_TOKEN removed. Keep runner pins, resource bounds and main/tag secret gates. A no-secret cold-install workflow imports the actual CLI in the same pinned runner and512Mi budget; no deployment or forge contact occurs. Validation:25 deployment/concurrency/workflow tests pass, ESLint scripts passes,60 workflow event renderings and strict Woodpecker lint pass. Local single-package frozen install and CLI import pass. task is unavailable locally; actual Task entry point and resource-bounded cold run are required in CI. Owner will wait for green PR pipeline before validator review and for trusted-main deploy-access success after merge before the approved receipt release. Rollback: revert this commit; it changes tooling installation only and makes no GitOps or database mutation. Receipt rollback artifact and Morten's migration/release approval are retained on parent22d19043. Production remains0.13.0. DevOps/Security reviews required before merge.
fix(ci): isolate deployment tooling dependencies
All checks were successful
ci/woodpecker/pr/deploy-tools Pipeline was successful
Details
ci/woodpecker/pr/quality Pipeline was successful
Details
ci/woodpecker/pr/image-agent Pipeline was successful
Details
ci/woodpecker/pr/docs Pipeline was successful
Details
ci/woodpecker/pr/image Pipeline was successful
Details
ci/woodpecker/push/deploy-tools Pipeline was successful
Details
ci/woodpecker/push/docs Pipeline was successful
Details
ci/woodpecker/push/quality Pipeline was successful
Details
4804755c3d
morten-olsen commented 2026-10-08 19:17:18 +02:00
Owner

Merged by Morten's Claude Code session, which is taking this rollout over end to end. One more blocker: #45, because a main-targeted draft would fail deploy-release's target_commitish check. That session will publish v0.14.0 once #45 is merged and will verify the deployment. Please don't publish the release in parallel.

Merged by Morten's Claude Code session, which is taking this rollout over end to end. One more blocker: #45, because a main-targeted draft would fail deploy-release's target_commitish check. That session will publish v0.14.0 once #45 is merged and will verify the deployment. Please don't publish the release in parallel.
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ai/mission-control!44
No description provided.