Changelog Roundup for November 9, 2026

The biggest change this week is for everyone who deploys: a site can now be up to 1 GiB, ten times the old limit. Operators should update their nodes so they can hold the largest packages.

For node operators

Sites can now be up to 1 GiB. Packages over 500 MiB go only to nodes running v0.0.132 or later, because older versions cut a fetch off at 500 MB. Transfers to your node now fail only when they stop moving. If a large package is cut off on its way, your node picks up where it stopped. Update your node to hold the largest packages.

Monthly operator payouts are now worked out from the whole month, once. The monthly close counted only the last seven days of a month’s bandwidth, and a restart on our side could close a month a second time. It now counts every day and closes each month once. No operator has been paid during the open beta, so no payout was wrong. You don’t need to do anything.

For customers

Sites can now be up to 1 GiB, up from 100 MiB. ee-cdn-cli 0.5.0 asks for the limit, streams uploads from disk and refuses an oversized site before uploading anything. Update to 0.5.0 or later, because older versions still stop at 100 MiB. If you use the deploy Action at @v1, you’ll get the change with its next release. If you’ve pinned an exact release, move to the first one that runs 0.5.0.

Portal deploys are now packaged the same way as ee-deploy, also up to 1 GiB. Deploys now run in the background and show each stage as it runs. Files follow the same rules as ee-deploy, so .git/, .DS_Store and ee.jsonc are no longer published. If a deployment target names a folder such as blog, its files are now served from the root. Check your site’s addresses after its next deploy, then update links or add redirects for any that moved.

Redeploying an unchanged Level 1 or Level 2 site, and rolling back at any level, now works. From 0.5.0, ee-cdn-cli reuses content that’s already stored instead of uploading it again. For a Level 1 site, pass the key from its first deploy with --key or EE_CDN_LEVEL1_KEY. Without that key, the CLI stops and deploys nothing. Your links keep working. The portal still refuses to redeploy an unchanged Level 1 site.

Insights now shows usage per site for the range you choose. You can pick 7 days, 30 days or a custom range within the last year. You can also filter to one site, see each site’s share of bandwidth and export a CSV. Each workload page now has a Usage tab. Per-site figures can be up to an hour behind the workspace totals.

Insights can also show days in your local time, and today so far. A UTC | Local switch groups days by your browser’s time zone. Local works for ranges starting on 28 October 2026 or later. The page opens in UTC, so bookmark a Local view if you want to keep it.

You can now redirect a whole domain from _redirects. A rule such as https://old.example.com/* https://new.example.com/:splat 301! works once the old domain is claimed and bound to your site. Domain rules run before path rules wherever they sit in the file, and they allow only 301 and 302. Write https:// rules, because an http:// rule on its own never fires. This works on Level 0 sites only.

AI agents that ask for Markdown can now get your page’s Markdown copy at the same address. Add # ee:markdown on to _redirects. A request for /cli/ that prefers Markdown then gets /cli.md, while browsers still get your HTML. This works on Level 0 sites only.

Packaging a large site no longer needs memory to match. Packaging now writes to disk as it goes, so a large site can be packaged on a laptop or a small CI runner, and the packages it makes are byte for byte the same. If you pin --builder-version, pin the builder published on 3 November or later, or remove the pin.

Monthly bills are now worked out from the whole month, once. No customer has been charged during the open beta, so no bill was wrong. You don’t need to do anything.

For everything else, see the full changelog.