Skip to content

ci: drop the Target B managed build job - #240

Merged
pythonlearner1025 merged 2 commits into
mainfrom
ci/drop-target-b-job
Sep 6, 2026
Merged

ci: drop the Target B managed build job#240
pythonlearner1025 merged 2 commits into
mainfrom
ci/drop-target-b-job

Conversation

@pythonlearner1025

Copy link
Copy Markdown
Member

What part this touches

  • .github/workflows/ci.yml is the check matrix that runs on every push and pull request.
  • Target B is the blitz.dev managed deployment: the control plane emitted as plain source files instead of a bundled Worker. The emitter is packages/control-plane/scripts/build-blitzdev.mjs.
  • The Target B managed build (blitz.dev) job ran that emitter and eight vitest files under BLITZDEV_MANAGED=1.

The gap

  • The job was added on 2026-08-21 because nothing else in CI built the managed artifact, and a missing manifest entry once shipped a deploy that failed every route.
  • Since then the JavaScript job runs npm test with BLITZDEV_MANAGED=1. The same eight suites run there, closure gate included, and blitzdev-emitter.test.ts imports the real emitter.
  • The job's only extra work is the blitzdev:build command line. It costs about 52 s per run, and the matrix runs twice per pull request.
  • Target B itself is dormant: plans/BLITZDEV-PLATFORM-ASKS.md says its production promotion waits for a platform lift, and the emitter last changed in August.

The fix

  • Remove the blitzdev job and its comment block from ci.yml.
  • Nothing else changes. The emitter, its tests and the blitzdev:build script stay in the tree.

The risk trade

  • The blitzdev:build command line itself no longer runs in CI. The emitter module it calls is exercised by blitzdev-emitter.test.ts in the JavaScript job. If the command-line wrapper ever drifts from the module, the first person to run it finds out.
  • Reviving Target B needs no CI change: the suites still run on every push.
  • I rejected folding the build step into the JavaScript job. It would add the same redundant minute to the job every product change waits on.

Tests

  • node --test test/deploy-tooling.test.mjs in packages/control-plane parses both workflows and passes.
  • The removed job has no references in docs, tests or scripts.
  • GitHub validates the workflow on the first run of this branch.

Deploy

  • The workflow file ships itself. The next push runs five jobs instead of six.
  • Rollback: revert the commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_01So15XYnmh9Hfx9xdNgG1Yu

pythonlearner1025 and others added 2 commits September 5, 2026 16:42
The JavaScript job already runs the same eight managed-toolchain suites
with BLITZDEV_MANAGED=1, and the emitter test imports the real emitter.
The job's only extra work was the blitzdev:build command line. Target B
is dormant until the blitz.dev platform lift.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01So15XYnmh9Hfx9xdNgG1Yu
@pythonlearner1025
pythonlearner1025 merged commit 78d800e into main Sep 6, 2026
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.

1 participant