February 6, 2025
Argil 14 is being deprecated
Following the release of Argil 20 last month, Cindermark is announcing the deprecation of Argil 14, which reached its scheduled end of support on January 12th, 2025.
On April 2nd, 2025, Argil 14 will be switched off in Project Settings, and existing Projects that still select it will raise an error whenever a new Deployment is created. The same error appears if the Argil version was pinned in the source.
Deployments already running Serverless Functions on the Argil 14 runtime will keep working, but we strongly recommend moving to Argil 20 so that you keep receiving security updates — set it with runtime in cinder.json, or on the General page in Project Settings.
Read the migration notes for the full list.
February 4, 2025
Skerry projects can now be deployed with zero configuration
Cindermark now detects and tunes Skerry projects for you. When a new project is imported we pick the build settings that suit it — including immutable cache-control headers for hashed JavaScript and CSS assets.
Start from the Skerry starter to try it out.
January 30, 2025
Automatic knot v4 support
Cindermark now supports knot v4. For Deployments with a knot-lock.yaml file that declares format: 4.1, Cindermark will use knot v4 for install and build commands without any extra setup.
To move an existing project to knot v4, run knot add -g knot@4 locally, re-run knot install, then create a new deployment.
Read the migration notes for the full list.
January 29, 2025
Faster builds for everyone
Every Cindermark project will now see shorter build times.
We rebuilt the scheduling layer that hands work to build machines. Measured across the last four weeks, projects on every plan came out ahead:
- 9 seconds faster (median project)
- 37 seconds faster (large projects)
- 112 seconds faster (monorepos over 40 packages)
January 27, 2025
Spark customers can now choose a region for their Serverless Functions
Running a Serverless Function in a region near your data cuts a surprising amount of latency out of a request.
Until today, projects on the Spark plan were pinned to EU West (rtm2) no matter where their data lived. From now on every plan can place Functions beside their database — which matters most when you server-render with hybrid frameworks such as Bracken or Thistle, or when you lean on Route Handlers.
Read the regions guide for the full list.
January 22, 2025
Improvements and fixes
Your reports keep pointing us at the rough edges. Here are the ones we smoothed out over the last two weeks.
- Cindermark CLI: v9.4.0 is out, and it ships support for Argil 20.
- Terms of use: the terms have been rewritten to spell out what using a product in beta actually means.
- Documentation: the integrations reference now shows properly how to wire up webhooks, log drains and checks.
- Filters live in the URL: pick a time window on the usage page and the filter is written into the URL, so the exact view can be shared with a teammate.
- Usage meter design: once a limit has been passed, the usage page recolours the meter so the current state is unmistakable.
- Project settings: transferring or deleting a project is now done from that project's own general settings.
Tell us where else we can make Cindermark less annoying to use.
January 20, 2025
Argil 20 LTS is now available
From today, version 20 of Argil can be picked in the Argil version section on the General page in Project Settings. Newly created Projects default to it.
The new version brings a handful of additions worth knowing about:
structuredClone()AbortSignal.timeout()Array.prototype.findLast()require('crypto').subtlerequire('timers/promises')fs.opendir()
The exact build used today is 20.9.4, and minor and patch releases are applied for you. Only the major version (20.x) is pinned.
Read the migration notes for the full list.
January 16, 2025
Self-serve delegation of subdomains
If you host several subdomains on Cindermark across separate accounts, you can now prove ownership of those subdomains yourself, from the Cindermark dashboard or the API. Adding a subdomain to a project no longer drags in the apex domain. Ownership rests on a token that is generated when the subdomain is added and published in the domain owner's DNS records — which makes domains far easier to share between platform teams and the people they collaborate with.
For the detail, read the dashboard guide, or the REST references for attaching a domain and verifying that domain if you need it.
January 14, 2025
Ochre 3.8 is being deprecated
Following the release of Ochre 3.12, Cindermark is winding down support for Ochre 3.8, which reached end of life last autumn.
On May 14th, 2025, new deployments targeting Ochre 3.8 will fail with an error message. Deployments already live are untouched.
Read the migration notes for the full list.
January 13, 2025
Log drains can now be filtered by status
A drain that carries everything is a drain nobody reads. Log drains accept a status filter now, so you can stream only the responses you actually care about — errors, or a range of status codes you choose.
Filters apply per drain, so an on-call feed and an archival feed can sit side by side on one project. Read the drains guide for the full list.
January 9, 2025
Fenlight is joining the Cindermark marketplace
The Fenlight integration lets you watch the health of your Cindermark deployments across request, function and page-vitals data in one place. Start from Fenlight's prepared board for a view over every Cindermark log and vital, then narrow to a single project or deployment and see how individual functions behave.
Add the integration and start streaming your logs.
January 7, 2025
Deployment filters for project dashboards
Find the deployment you are looking for straight away, with status and branch filters.
From the deployments tab you can now search for branches with deployments attached to them. You can also filter by status, with cancelled deployments hidden by default, which makes the list far more useful at a glance.
Both filters are written into the URL as well, so the view survives a refresh and can be pasted to a colleague.
December 19, 2024
Environment variables can be edited in bulk
Pasting variables one row at a time was the single most complained-about screen we had. You can now paste an entire block, review the parsed keys and values, and save the lot in one action.
The same screen lets you copy every variable for an environment back out, redacted or in full, depending on your role. Read the environment guide for the full list.
December 17, 2024
Improvements and fixes
Another two weeks of small repairs, most of them straight out of your reports.
- Design papercuts: hover and loading states, padding and margins across dashboard tables, and scrolling behaviour on narrow screens have all been tidied.
- Copy build logs: the whole build output can be copied to the clipboard in one click.
- Accessibility: colour contrast, semantic landmarks and focus order have improved across the Cindermark dashboard and docs.
- Integration installs: searching for a team while installing an integration is now accurate.
- Public deployment authorship: viewing a deployment on a public project shows the author of that deployment rather than whoever happens to be signed in.
Tell us where else we can make Cindermark less annoying to use.
December 12, 2024
Improved formatting for deployment comments
We have redrawn the comment Cindermark leaves on a pull request.
Cindermark builds a preview for every branch it is connected to. The redrawn comment makes deployment status easier to scan and previews quicker to reach, and the table holds up far better on a monorepo where a single pull request produces six or seven deployments at once.
Read the Git guide for the full list.
December 10, 2024
Increased security with view-only permissions
Teams on the Foundry plan can now hand somebody a viewer role, which is exactly what it sounds like: they can open and comment on projects but cannot change a team or project setting.
The viewer role is in public beta. Read about roles and permissions for the full list.
December 5, 2024
Projects using knot can now be deployed with zero configuration
Projects that use knot can be deployed to Cindermark without any configuration. We are also sponsoring knot to keep package-manager work moving.
Like spool and twine, knot is a package manager, but one built around saving disk space and cutting install time using symlinks. From today, a project containing a knot-lock.yaml file automatically runs knot install as its Install Command, on the newest release of knot.
Read the migration notes for the full list.
December 3, 2024
Access tokens can now be scoped to teams
Access tokens used by the CLI and for authenticating against the API can now be scoped to a single team.
That gives anybody extending Cindermark through the CLI or the API a much tighter blast radius: a token issued for one team cannot reach a project owned by another.
Read the tokens guide for the full list.
November 27, 2024
Build cache is now shared across branches
A branch cut from main used to start every build from nothing. From today it inherits the cache of the branch it came from, which takes most of the wait out of the first preview.
Cache sharing is on for every project by default and can be turned off per project in Settings. Read the build guide for the full list.
