Changelog Roundup for September 28, 2026

Updates
This Week at Evolving Edge: what changed on the network, for the people who run it and the people who build on it

The most important change this week is for node operators running Docker: recreating the container no longer turns your node into a brand new one with its Active Node Hours back at zero. For customers, any static site can now be published from the command line.

For node operators

Docker nodes now keep their identity when the container is recreated. Until now, every recreate or image pull enrolled the node as new, resetting its Active Node Hours and removing its leaderboard place without telling you. To get the fix, download the current Compose file and recreate the container, then leave both volumes alone, because deleting either one makes the node new again. Your node will reset one more time as it picks this up. The identity it had depended on a random hostname that is already gone, so there is nothing to recover it from. After that it should not reset again.

Some systems don’t provide a machine ID, including some container images and appliance platforms. Nodes on those systems now keep their identity too. From edge-node v0.0.104, a node that finds no machine ID creates one and keeps it in its home directory. The key protecting its stored credentials also uses that ID now, where before it came from the hostname alone. Most computers, and Docker with our Compose file, need nothing from you. In any other container, put the node’s home directory on persistent storage. Affected nodes pair once more after updating and start from zero one last time.

If you forwarded a port on your router by hand, the gateway eligibility list kept telling you to forward one anyway. A manually forwarded port now counts. If your node is reachable, the requirement passes, however you made it reachable.

The edge node’s source is now public for review under MPL-2.0. It covers the parts that handle the content your node serves. Issues and questions are welcome, but it isn’t open for contributions.

The network map now marks the 47 U.S. markets where we will operate gateway nodes, alongside live node counts. When nodes start reporting in one of those markets, a Gateway will be deployed there to support them.

For customers

ee-cdn-cli publishes any static site from the command line. Until now, the Astro integration was the only supported way to publish. Point the tool at your build’s output folder and it packages the files, uploads them and tells you how to confirm your domain is serving. It reads your deploy token from EE_CDN_TOKEN, and --dry-run packages the site without uploading it.

Your site’s own 404 page is now served. If your build includes a 404.html, visitors who ask for a missing page see it in your design, with nothing to configure. It keeps a 404 status, so search engines won’t index it as real content.

Sites without their own 404 page get a branded page that no longer reveals where we store your files. The old plain-text reply named an internal storage path and sent no cache headers, so a file could stay missing for visitors after you published it. The new page carries no internal detail and has its own cache policy.

The deploy preview link now works for projects without a custom domain. Before, it returned a 404. If the right host can’t be determined, no link is shown.

If your security team wants to know what the machines serving your content do with it, the edge node’s source is now public. Read the code that touches your content covers where to start and what reading the source does and doesn’t prove.

For everything else, see the full changelog.