Repo-level changelog for the static.polygon.technology HTTP endpoint and the
repository's tooling. The @polygonlabs/meta npm package has its own
changesets-managed changelog at
packages/meta/CHANGELOG.md.
First changelog entry, marking the endpoint's move to Cloudflare.
static.polygon.technologyis now served from Cloudflare Workers static assets. The nginx Docker image and its AWS ECS / GCP deploy pipelines are removed (Dockerfile,nginx.conf,deployment.yml,build_and_deploy.yml,deployment_gcp.yml,.github/taskdef/). The image was internal deploy tooling only — it was never published to a public registry. Self-hosting the content needs nothing more than a static file server pointed atnetwork/; the retired nginx setup remains available in git history.- Deployment is trunk-based via
wrangler(.github/workflows/deploy.yml): pushes tomasterdeploy staging (static-staging.polygon.technology), and@polygonlabs/metarelease tags deploy production, in lockstep with the npm publish. - Missing paths now return a real
404. The retired nginx config served the health-check HTML page with200for any unknown path. - CORS: preflight
OPTIONSis answered by a minimal worker script (worker/worker.ts) with204andAccess-Control-Allow-Origin: *,Allow-Methods: GET, HEAD, OPTIONS,Allow-Headers: Content-Type, Authorization,Max-Age: 86400; asset responses carryAccess-Control-Allow-Origin: *via_headers.POSTis no longer advertised (nothing accepts a write), but theContent-Type/Authorizationallow-headers are load-bearing: maticjs sendsContent-Typeon its GETs, so browsers preflight — an initial Cloudflare revision shipped without the worker, returned 405 to preflights, and broke browser maticjs consumers until the worker restored them (#194). - Responses now carry
Cache-Control: public, max-age=300.
/network/index.js(a CommonJSNetworkclass predating the@maticnetwork/meta2.x package split) is no longer served. Use the@polygonlabs/metanpm package for typed access, or fetch the JSON tree directly.