Skip to content

refactor(cli): remove custom website release machinery - #9

Merged
WillieCubed merged 1 commit into
mainfrom
codex/remove-website-release-machinery
Oct 11, 2026
Merged

WillieCubed merged 1 commit into
mainfrom
codex/remove-website-release-machinery

Conversation

@WillieCubed

Copy link
Copy Markdown
Contributor

TL;DR

Remove the custom company-website release subsystem from release-engineering. Frontends use pinned native framework/OpenNext/Wrangler commands and conventional GitHub Actions in their product repositories. Preserve native and package release infrastructure.

Changes

  • Remove the website Workers adapter, custom Cloudflare recovery API/CAS/journal, cache seeder, release identity protocol and Mintlify deployment-inspection client/CLI.
  • Remove the corresponding framework/cache/recovery fixtures and tests, framework-runtime CI job, frontend-only suite flags and obsolete website inventories/instructions. Retain historical evidence in Git history and the migration workspace.
  • Restore the pre-existing Pages/Vercel deploy_site implementation; preserve standalone Worker, Cloud Run, native signing/notarization, package publication and distribution adapters.
  • Preserve candidate/promotion workflows, root/source/lock/toolchain guards, managed-credential precedence and approval/provenance checks used by native/package consumers.
  • Keep Mintlify's own renderer/Git publisher. No replacement custom transport, archive manifest, recovery client, activation flag or workflow is introduced.

Reviewed head: b8ca109dc3971337d61bd6688fa5b098ed2d0c1a, based on fetched main a13ccabcda7a2c3b7321fe412d2397f25df04d29. Python compilation, touched-source Ruff syntax/undefined-name checks, actionlint for all workflows and diff checks pass. Source comparison confirms twelve native provider functions are byte-identical and the retained legacy site adapter matches its pre-website implementation. Normal local commit completed without bypass. No new/manual tests, installations or provider requests ran; automatic existing CI supplies separate execution evidence.

Follow-ups and Next Work

Integrate product caller cleanup before consuming a future runtime that removes these website commands. Published runtime tags/assets are immutable and unchanged. This PR does not merge, tag, publish, deploy, provision or change credentials/permissions. The separate S3 transport draft PR #6 remains untouched and is obsolete under the native-tooling direction; its disposition requires coordination. Website runtime/backend/passkey/waitlist acceptance and any production cutover remain separate from this source cleanup.

Use native framework and provider tools for company websites instead of
maintaining frontend cache, inspection, candidate and recovery adapters.
Remove their fixture suite and framework CI job while preserving native
and package release workflows, guards and legacy distribution adapters.

Co-authored-by: Codex <noreply@openai.com>
@WillieCubed
WillieCubed marked this pull request as ready for review October 11, 2026 20:32
@WillieCubed
WillieCubed merged commit 37fe36f into main Oct 11, 2026
2 checks passed
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