chore(deploy): retire AWS/GCP pipeline; deploy production on release tags#193
Merged
Conversation
MaximusHaximus
marked this pull request as ready for review
July 8, 2026 19:01
MaximusHaximus
force-pushed
the
chore/retire-legacy-deploys
branch
from
July 8, 2026 19:06
d6405c0 to
684f337
Compare
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
MaximusHaximus
force-pushed
the
chore/retire-legacy-deploys
branch
5 times, most recently
from
July 8, 2026 19:48
66b034e to
8bccc0f
Compare
|
The endpoint serves from Cloudflare Workers static assets, so the nginx image and
its AWS ECS / GCP deploy pipelines (Dockerfile, nginx.conf, deployment.yml,
build_and_deploy.yml, deployment_gcp.yml, .github/taskdef/) no longer serve
anything and are removed. The image was internal deploy tooling, never published
to a public registry; self-hosting the content needs only a static file server
over network/, and the old setup remains in git history.
deploy.yml now deploys production on the @polygonlabs/meta release tag, in
lockstep with the npm publish, so the HTTP endpoint and the npm package — two
surfaces of one network/ tree — cannot drift; pushes to master deploy staging and
workflow_dispatch stays as the escape hatch. Environment resolution is plain bash
that fails closed on unexpected inputs or refs, instead of a ${{ }} ternary chain
whose short-circuiting silently falls through on falsy operands.
The staging hostname becomes static-staging.polygon.technology, matching the
<name>-staging convention of our other frontends.
A root CHANGELOG.md is introduced (entry 1.0.0) for the endpoint's
consumer-visible changes — real 404s, the read-only GET/OPTIONS CORS surface, the
cache header, and the /network/index.js removal — with a CLAUDE.md policy to
maintain it whenever the repository's capabilities change. Remaining docs and
config comments now describe the system as it is rather than the migration that
produced it.
MaximusHaximus
force-pushed
the
chore/retire-legacy-deploys
branch
from
July 16, 2026 10:37
8bccc0f to
13593d8
Compare
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
1 participant
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.
What
Finalizes the move of
static.polygon.technologyonto Cloudflare Workers static assets (#190–#192). The endpoint has been serving from the Worker since 2026-07-08, byte-verified against this repository'snetwork/tree.Dockerfile,nginx.conf,deployment.yml,build_and_deploy.yml,deployment_gcp.yml,.github/taskdef/. Every duty nginx had is replaced, not dropped: content serving by Cloudflare's static-asset layer, response CORS/caching headers bypublic/_headers, and CORS preflightOPTIONShandling by theworker/worker.tsshim (fix(deploy): answer CORS preflight OPTIONS from a worker script #194). They were kept briefly as a rollback path and are no longer needed; rollback is now redeploying a previous Worker version viaworkflow_dispatch. The image was internal deploy tooling only (never published to any public registry) — self-hosting this content needs nothing more than a static file server pointed atnetwork/, and the old setup remains available in git history.@polygonlabs/metarelease tags, in lockstep with the npm publish, so the HTTP endpoint and the npm package (two surfaces of onenetwork/tree) cannot drift. Pushes tomasterdeploy staging;workflow_dispatchremains the manual escape hatch for either environment.${{ }}expression chain with explicit bash that fails closed on unexpected inputs or refs instead of falling through to a default.static-staging.polygon.technology, matching the<name>-stagingconvention used by our other frontends.CHANGELOG.md(first entry1.0.0) documenting the endpoint's consumer-visible changes — real404s for missing paths, the CORS surface,Cache-Control: public, max-age=300, and the removal of/network/index.js(superseded by the@polygonlabs/metapackage).CLAUDE.mdgains the policy of maintaining it for future capability changes.Rebased onto master after #194 (the CORS preflight fix). The pre-outage comments claiming the
Authorization/Content-Typeallow-headers were a surface "that never existed" are corrected — they're load-bearing for maticjs's preflights and now live in the worker's OPTIONS response; the CHANGELOG's CORS entry now records the real surface (GET, HEAD, OPTIONS+ worker-answered preflights) and the incident. The[env.staging]comment also documents thatstatic-staging.polygon.technologyhas an existing externally-managed DNS record, so staging deploys fail harmlessly at domain registration (code 100117) until SPEC swaps the record ontopolygon-static-stagingin the CF dashboard — same sequence as the apex cutover.No changeset — all changes are outside
packages/meta/.