CLI changelog
ee-deploy and the framework integrations that publish sites to the CDN.
Deploying a site whose content hasn't changed no longer fails
Deploying an unchanged Level 0 site again was refused with "workload already exists with different bytes", because each build stamped its time into the package. Identical files now build identically. Encrypted sites and rollbacks still fail.
ee-cdn-cli finds your output folder and keeps .git out of what it publishes
ee-cdn-cli can now work out your build's output folder, turn on trailing-slash and clean-URL handling with a flag, and pin the builder version. Builds leave out version-control folders and refuse links that point outside the site.
ee-cdn-cli no longer writes Level 1 keys into your built pages
Built pages carried each Level 1 workload's key in the HTML, readable by every cache in front of the site. From 0.2.0 the key is left out by default and delivered in the address fragment instead, and embedKey opts back in.
Publish any static site with ee-cdn-cli
ee-cdn-cli publishes a folder of static files to the CDN from the command line, so sites built with Hugo, Eleventy, Jekyll, Publii or by hand can deploy without a framework-specific integration.
Level 1 and Level 2 key fixes reach the deploy CLI
The recent key-handling fixes have now been made in the deploy CLI and its Astro integration too, so every tool we maintain treats keys the same way. The CLI isn't published yet, so there is nothing for anyone to update.
Deploy tokens keep every role you select
A deploy token created with both roles ticked lost its workload role, so every deploy with it was refused with "Insufficient permissions". New tokens keep every role you select. If you have a token affected by this, create a new one.
Sites deployed from CI now appear in the portal
Sites published from CI or the command line served normally but left the portal's Files and Deployments tabs empty, and their traffic was missing from project analytics. New deploys now show up in the portal just as portal deploys do.