Repository navigation
refactor(cli): remove custom website release machinery - #9
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
deploy_siteimplementation; preserve standalone Worker, Cloud Run, native signing/notarization, package publication and distribution adapters.Reviewed head:
b8ca109dc3971337d61bd6688fa5b098ed2d0c1a, based on fetched maina13ccabcda7a2c3b7321fe412d2397f25df04d29. 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.