# Changelog Roundup for November 16, 2026

> A security fix stops nodes from sending their credentials to other nodes. Node fixes for enrollment, sign-in tabs and Mac logs, plus a new ee-migrate command for moving sites to Evolving Edge.

Published: November 16, 2026 · Author: John Federico · Category: Updates · Tags: roundup, changelog

Source: https://blog.evolvingedge.ai/post/changelog-roundup-2026-11-16/

The most important change this week is a security fix for node operators. From v0.0.133, your node no longer sends its credential to other nodes when it copies a site, so please update.

## For node operators

[Your node no longer sends its credential to other nodes when copying a site][1]. Until now, your node sent its node key or sign-in token with each copy request, and the operator of the node it copied from could read it. From v0.0.133 it sends only its node ID, and copies work as before. No incident has occurred. Credentials that were already sent aren't revoked. Update to v0.0.133 or later.

[Copies between nodes no longer count as deliveries][2]. You're no longer credited for copies your node serves to other nodes, and what you deliver to visitors is credited as before. From v0.0.133, a copy needs a signed ticket, and a request without one counts as an ordinary delivery. Update to v0.0.133 or later.

[Your node keeps its enrollment when its hostname changes][3]. Saved credentials were tied to the hostname, so a hostname change sent the node back to browser sign-in. This is common on Macs and on networks that assign hostnames. From v0.0.134 they're tied to the hardware ID instead. Update to v0.0.134 or later. If your node has already lost its enrollment, set its old hostname back once first.

[A node running as a service no longer opens browser tabs to sign in][4]. A background node that couldn't open its enrollment opened a new sign-in tab every time it restarted, and finishing one enrolled the machine as a second node. From v0.0.134 it writes the sign-in link to its log instead. If it can't open an enrollment, it waits for it rather than replacing it. Update to v0.0.134 or later.

[Delivery credit now comes from visitors' verified receipts][5]. When a visitor's browser verifies a piece your node sent, it sends a receipt, and you're now credited from those receipts rather than from your node's own count. There's nothing to set up.

[Sites are now copied to operator nodes in the metros where visitors ask for them][6]. Only nodes with free space are used. A node that restarts keeps its place for 10 minutes, so updating the node software doesn't move copies around. You don't need to do anything.

[Mac node logs no longer grow without limit][7]. From v0.0.134, a node running as a service on macOS rotates its logs at 20 MB and keeps three older copies. If you run a node on a Mac, update it.

## For customers

[`ee-cdn-cli` no longer passes your deploy token to the packaging tool][8]. From 0.4.1, the packaging tool gets only the basic system settings it needs, so your deploy token and other credentials in your CI job aren't passed to it. No incident has occurred. If you run the CLI yourself, update to 0.4.1 or later. The deploy Action at `@v1` already includes the fix. If you've pinned `@v1.0.0`, move to `@v1.0.1`.

[Revoked deploy tokens are refused even while token checks are unavailable][9]. Before this fix, uploads could skip the revocation and project checks in some cases. An upload that can't be checked is now refused with a message to retry shortly, so run it again in a minute. Changing domain mappings now needs write permission.

[Bring your redirects and headers when you move a site to Evolving Edge using `ee-migrate`][10]. From `ee-cdn-cli` 0.5.1, the new `ee-migrate` command translates the redirects and headers in your previous host's configuration file into `_redirects` and `_headers`. It reports every setting it carried over, changed or left out. Run it on the site's folder before you deploy.

[`ee-migrate` now writes a CI workflow that builds and deploys your site][11]. From 0.6.0, it turns your previous host's build settings into a GitHub CI workflow that deploys on every push. Build variables that look like credentials are read from repository secrets. Rotate them, because they were committed in plain text. Check the log of the workflow's first run.

[Sites are copied to nodes in the metros where visitors ask for them][12]. Once a Level 0 site with a verified domain gets 5 requests in a day from one metro, two operator nodes there get copies. Your site's addresses stay the same.

[Copies of your site between nodes no longer count toward your usage][13]. From 10 November, your usage figures count only what visitors receive. Earlier days aren't recalculated.

For everything else, see the [full changelog][14].

[1]:	https://changelog.evolvingedge.ai/2026/11/node-credential-not-sent-to-peers/
[2]:	https://changelog.evolvingedge.ai/2026/11/node-copies-not-counted/
[3]:	https://changelog.evolvingedge.ai/2026/11/node-keeps-enrollment-after-hostname-change/
[4]:	https://changelog.evolvingedge.ai/2026/11/service-node-no-browser-tabs/
[5]:	https://changelog.evolvingedge.ai/2026-10-01-deliveries-credited-from-verified-receipts/
[6]:	https://changelog.evolvingedge.ai/2026/10/sites-copied-to-busy-metros/
[7]:	https://changelog.evolvingedge.ai/2026/11/mac-node-logs-rotate/
[8]:	https://changelog.evolvingedge.ai/2026/10/ee-builder-no-deploy-token/
[9]:	https://changelog.evolvingedge.ai/2026-10-01-revoked-deploy-tokens-always-refused/
[10]:	https://changelog.evolvingedge.ai/2026/11/netlify-toml-migration/
[11]:	https://changelog.evolvingedge.ai/2026/11/ee-migrate-deploy-workflow/
[12]:	https://changelog.evolvingedge.ai/2026/10/sites-copied-to-busy-metros/
[13]:	https://changelog.evolvingedge.ai/2026/11/node-copies-not-counted/
[14]:	https://changelog.evolvingedge.ai
