When you run the graphcdn push command we immediately validate your configuration file to ensure it is correctly formatted.

However, the validation error messages were not as helpful as they should be. We have overhauled them in the latest release of the CLI (v0.4.3) to make sure they precisely explain the issue(s):

$ graphcdn push
Error:  Invalid graphcdn.yml:
- schema: Required
- defaultCacheControl.scope: Expected string, received number

Install the latest version of the CLI by running the npm install graphcdn@latest command in your project's directory.

Our gateway wasn't built with very large (megabytes) responses in mind, and thus would sometimes hang or even crash when lots of data was being sent through it.

As of today, we have added support for responses in the dozens of megabytes. We've also added a pass-through for responses that are too large for us to handle, so even if you're above our gateway's limit your users won't notice a thing.

On your dashboard, you will from now on see the familiar Intercom bubble in the bottom right corner. If you click on it you can start chatting with us right away:

If you have any questions about GraphCDN or your usage, you can always reach us there!

We've completely revamped service dashboards to show in-depth analytics about your GraphQL API!

• They now show:
• Request counts split into cache hits, passes and misses
• Cache hit rate, p95 cold response time, origin bandwidth saved as well as user time saved
• All the queries services received from clients
• All the errors services received from origins
• The pages, countries and user agents sending requests to services

Here is a screenshot what that looks like for one of our demo services:

In order to make it as easy as possible to manage staging or dev environments, the graphcdn CLI now supports environments in the graphcdn.yml!

Here is an example of what that looks like:

name: my-product
schema: api.product.com/graphql
originUrl: api.product.com/graphql
environments:
  staging:
    name: my-app-staging
    schema: staging.product.com/graphql
    originUrl: staging.product.com/graphql

You can then push to or pull from the staging environment by running the corresponding commands with the --env argument:

# Push to staging
graphcdn push --env staging
# Pull from staging
graphcdn pull --env staging

Learn more in the environments documentation.

Over time we cluttered responses from GraphCDN services with a bunch of unnecessary custom headers we use for debugging.

As of today, only the most important ones that are useful for debugging your caching behavior are sent back:

• gcdn-cache: can either be HIT (was returned from cache), miss (should have been cached but wasn't), pass (should not be cached)
• gcdn-scopes: the scopes that applied to the query
• gcdn-scope-value-missing: whether at least one scope value required in the query was missing (i.e. whether this was treated as a "public" request)

GraphCDN now supports queries with special characters (like emojis 🙈) in them, whether in variables or not! 🙌

Previously, they would sometimes error as our parser didn't handle all of them correctly. 😅

Rather than making that an explicit setting, we will from now on simply inherit your origin's preferences by passing introspection requests through to it!

If you origin has introspection enabled, your GraphCDN service will also allow introspection. If you origin does not have introspection enabled your GraphCDN service will also not allow introspection requests.

Open your GraphCDN dashboard and you will see something new: organizations. They allow you to group multiple services under one umbrella with consistent access control, billing and management.

We have automatically created organizations for all of your services, but you can of course also create a new one for your company specifically:

Instead of the old, tedious way to configure caching per GraphQL type or field, we now have cache rules!

Head over to the "Rules" tab in your service's dashboard and you will see your first rules already:

To upgrade your graphcdn.yml, simply run graphcdn pull and we will automagically rewrite your cache configuration into the new rules!