All months

Changelog · 2025-05

May 2025

Quant Cloud application hosting arrives in early access, with its own dashboard, an API and a set of GitHub Actions for deploying your applications.

4 updates across 4 products shipped this month.

New 3

Back to top
New GitHub Actions

Quant Cloud deployment actions

New GitHub Actions let you deploy containerised applications to Quant Cloud from your workflows. The actions are quantcdn/quant-cloud-ecr-action, quantcdn/quant-cloud-create-application-action, quantcdn/quant-cloud-compose-action, quantcdn/quant-cloud-environment-action and quantcdn/quant-cloud-environment-state-action. They sign in to the Quant Cloud image registry, create an application, create or update environments, and change the state of an environment, for example to redeploy it. They also translate a Docker Compose file into a Quant Cloud application definition. The image_tag_updates input of quantcdn/quant-cloud-compose-action lets you set a new image tag for each container, for example a tag from an earlier workflow step.

New KV stores

Item update endpoint

A new API endpoint updates a key-value store item in place, complementing the key-value store management API from October.

Related documentation: Update an item in a kv store

New Quant Cloud

Container application hosting

Quant Cloud is a new part of the platform for running containerised applications alongside your static sites. You define an application from a Docker Compose file and manage it from the dashboard or the new Quant Cloud API. Each application can have multiple environments. Quant Cloud supports per-container resource limits and health checks, scheduled cron jobs with run history, and request-based autoscaling policies. You can also see the status, logs and metrics of each container. Quant Cloud is in early access: contact our sales team to enable it.

Related documentation: What is Quant Cloud?

Fixed 1

Back to top
Fixed SDKs

Content deletion in the TypeScript content client

In @quantcdn/quant-client versions before 2.0.10 (the TypeScript client for the content API), awaiting project.delete() did not delete the path. The request was sent only when you called .first() on the result. From version 2.0.10, project.delete() sends the request and returns the API response, as project.publish() and project.unpublish() do from 2.0.9.

Remove any .first() call on the result of project.delete() when you upgrade to 2.0.10.