What changed in May 2026
The May 2026 changelog has the full details.
Trailing-slash redirects
Projects have a new "Redirect trailing slashes" option in the create and settings forms. When it is on, a request for a path such as
/about/gets a permanent (301) redirect to the same path without the slash. The redirect applies to static content that Quant serves, not to requests that a proxy rule handles. New projects have the option on, and existing projects keep their current behaviour until you turn it on.Cache-key purge on QuantGov
You can now purge by cache key on QuantGov projects, from the dashboard purge form and the API. One request invalidates all content tagged with a shared key. Soft purge is still not available for QuantGov projects.
CLI purge by key only
The
quant purgecommand no longer needs a URL path. Run it with only--cache-keysto purge by key. You cannot combine a path and--cache-keysin one command. This is available from CLI v6.2.0.Purge action inputs (v7)
The GitHub purge action has two new inputs.
cache_keyspurges by cache key instead of URL pattern.soft_purgemarks content stale, so it is served until fresh content is available.url_patternis now optional and cannot be combined withcache_keys.
By the numbers
- permanent redirect for a trailing slash
- 301
- purges by cache key with no path
- CLI v6.2.0
- adds cache-key and soft purge inputs
- Action v7
Who it is for
Government teams
QuantGov projects can now purge by cache key, so one request invalidates all content that is tagged with a shared key.
Site owners
Turn on trailing-slash redirects, so static content at a path that ends in a slash goes to the path without the slash.
CI pipeline owners
Purge by cache key in a CI pipeline, from the CLI with no URL path or from the GitHub purge action with
cache_keys.
How it works
The trailing-slash redirect is a project setting. When “Redirect trailing slashes” is on, a request for /about/ gets a permanent (301) redirect to /about. The redirect applies only to static content that Quant serves. Requests that a proxy rule handles are not redirected. New projects, including projects created through the API, have the option on by default. Existing projects keep their current behaviour until you turn it on.
A cache-key purge works on content that your origin tags. Your origin sends a Cache-Keys header with the response. One purge request then invalidates all content tagged with a shared key. May adds these ways to send that request:
- On QuantGov projects, from the dashboard purge form and the API.
- From the CLI, with only
--cache-keysand no URL path. - From the GitHub purge action v7, with the
cache_keysinput.
For example, a CI step can purge by key without a path:
quant purge --cache-keys <keys>In the purge action, set soft_purge to mark content stale. The stale content is then served until fresh content is available. Soft purge is not available for QuantGov projects.
Get started
Turn on the redirect
In your project settings, turn on the "Redirect trailing slashes" option.
Tag your responses
Send a
Cache-Keysheader from your origin on the content that you want to group.Purge in the dashboard
Use the cache key field in the dashboard purge form.
Purge from the CLI
Use quant purge with
--cache-keys, from CLI v6.2.0.Purge from GitHub Actions
Set
cache_keysin purge action v7. Read Scoping the purge.
Related: Explore Global CDN · Documentation · May 2026 changelog
Ready to try it on Quant?
Use the global CDN on your own project, or talk to our team first.