Changelog

What changed
in SuperCI

Every version, newest first. The dashboard shows the entries your control plane does not have yet, and updates it with one click.

Latest 0.20.4 · npx @superci/cli dashboard@latest --version

0.20.4

· Release notes

  • A preempted Modal Function stops its job in seconds. Modal stops one with SIGINT, which never reached GitHub’s runner: the job stayed in progress until GitHub gave up on the lost runner, about twelve minutes, every step red, and the control plane heard of it only when Modal started the same input again. Now the control plane is told at once and the runner interrupted, as on a spot machine AWS takes back: the job’s steps hear the interrupt and the job fails within seconds, then runs again once its run has finished. Found, measured on a real workspace and fixed by Taras Kornichuk (github.com/artile). Update your control plane for it.
  • A job whose machine was lost is not run again when its run passed without it (a job that may fail, continue-on-error): a new attempt would only cost a machine. By Taras Kornichuk.
  • A control plane in any AWS account or Modal workspace SuperCI is signed in to is changed with that one’s sign-in, whichever is in hand: created there (superci planes create modal --account=WORKSPACE), moved to and from, updated, deleted, its settings and keys written. A command naming one other than the CI’s own (planes update ID, planes delete ID, a move) used the first sign-in of its cloud, or refused, saying SuperCI was signed in elsewhere. Found and first fixed for Modal by Taras Kornichuk (github.com/artile), who tried it on real workspaces.
  • Deleting a Modal control plane deletes the Dict of each kind of its records too (…-k-…), not only its state and settings.
  • superci planes update ID with an id not known here says so. It updated the control plane in use in its place.
  • The expired keys of an AWS control plane in a further account are tidied in that account. They were looked for in the account in hand, and stayed.
  • Control planes are looked for in every Modal workspace signed in to, as in every AWS account: one in a further workspace was not found by a later command, or on another computer.
  • A sign-in its cloud ended in one AWS account or Modal workspace, beside others still signed in to, is said by that account or workspace (superci planes list, the dashboard, and each change that needs it) until it is signed in to again: superci login aws --add, superci login modal --add. It was forgotten without a word, its control planes and runners no longer shown. The others go on: a control plane in a further account or workspace is updated and deleted with its own sign-in when the first one’s has ended, which said to sign in with AWS first.
  • Updating or deleting a control plane in another account from the dashboard leaves the account in hand as it was. The pages and later changes went on with the other account’s sign-in.
  • A move between control planes is not stopped by an AWS sign-in that ended when neither of them is in AWS.
  • A command that changes a setting acts on the control plane named with --plane=ID (or SUPERCI_PLANE) when it is not the one in use: superci keys create NAME --plane=ID, its limits, its order. It was refused as not among the control planes here.
  • A move brings each kind of runner in its own account: AWS runners with the sign-in to the account they are in (it asked to sign in with AWS when another account was in hand), a Modal launcher in its own workspace (with that workspace not signed in to, it was deployed in the one in hand, where its jobs then ran and were billed), and a Cloudflare launcher in the account it is in (it went to the first account the Cloudflare sign-in reaches). One whose account is not signed in to is asked for before anything moves.
  • The control plane’s permissions read the AWS role in every account signed in to, with that account’s sign-in: a role in an account not in hand was shown as one to sign in for, and never read.
  • The control plane’s page offers Update for a control plane whose account or workspace is signed in to beside one that ended.
  • With several AWS accounts or Modal workspaces signed in to, a new control plane or runners outside the control plane’s own cloud are made only in the one named: superci planes create aws --account=ID, superci planes create modal --account=WORKSPACE, superci runners create aws --account=ID --region=R (the CI’s own AWS runners, while it has none), superci runners create modal --account=WORKSPACE. Without one, the command and the dashboard ask which, and nothing is made. They went into the one in hand. The dashboard’s own buttons name the one their row says.
  • A command naming a control plane with --plane=ID acts on it for that command alone. It became the one in use from then on where no control plane serves a code host, and deleting it was then refused as the one in use.

0.20.3

· Release notes

  • The control plane’s page says how many spot CPUs its account may run at once across every region its spot machines start in (300 in N. Virginia and 300 in Ohio: 600, 150 jobs of the default size), and each region’s own. Opened before the Runners page, it knew only its home region’s and said that alone.

0.20.2

· Release notes

  • A Modal control plane nobody uses for a week keeps everything it holds. Modal drops a Dict entry after seven days with no read or write of it, and such a control plane reads nothing: its sign-ins and device keys, its settings (the order, accounts and runners), its signing key, a moved control plane’s standby mark, and the days’ totals and the month’s spend that limits count were all lost after an idle week. Once a day it now reads every entry of each of its Dicts, never writing one back. Found by Taras Kornichuk (github.com/artile), who also made the settings it reads at each request be read entry by entry. Update your control plane for it.

0.20.1

· Release notes

  • A container’s processes may signal each other again on AWS’s Ubuntu 26.04 machines. RunsOn’s image of 2 November 2026 boots a kernel (7.0.0-1016-aws) under which Docker’s default AppArmor profile denied every signal inside a container (moby/moby#54099): Postgres never started, and builds that stop their workers failed with EACCES. Each Linux machine now sets kernel.apparmor_restrict_unprivileged_unconfined=0 before Docker and the runner start, kept in /etc/sysctl.d so a package installed by a job does not undo it. A machine runs one job and is thrown away, so this hardening of a shared host buys nothing there. Update your control plane for it.
  • Jobs boot the build of RunsOn’s image that this version of SuperCI was tested with, not each new one as it comes out: a new build reached every job at once before, as the one above did. Each kind of image (Ubuntu 24.04 and 26.04 on x64 and arm64, with GPUs, Windows Server 2025) is pinned to a build, and a release moves the pins. RunsOn keeps only its last three builds of each: once it has deleted the pinned one, jobs boot the oldest newer one left, and superci status and the dashboard say so and ask for an update. Your own copies of the image, in regions RunsOn does not publish in, are made of the pinned build too. Update your control plane for it.

0.20.0

· Release notes

  • Several AWS accounts run one CI’s jobs too: superci login aws --add, then superci runners create aws --account=ID --region=R [--name=WORD]. Each has its own role, machines, regions, spot notes and limits; a CI keeps one cache, in its first account, which machines elsewhere reach by links. Limits for any account: superci accounts update WORD. Each account’s bill is kept in the control plane, so every computer of a CI shows it.
  • A Modal launcher that has not been used for a while is woken before a job’s machine is asked of it. Starting from nothing took longer than a control plane waits, and the job then showed no machine with a note left over from waiting.
  • Several Modal workspaces run one CI’s jobs, each its own runner with its own limits and spend: superci login modal --add signs in to one more, and superci runners create modal --account=WORKSPACE [--name=WORD] adds it. A runner’s word stays for good. Deleting one keeps what it spent counting toward its account’s limit, and its word comes back only for the same workspace. Updating, moving and deleting a control plane handle each launcher with its own workspace’s sign-in and say which they could not reach. Sign-ins by Taras Kornichuk (github.com/artile).
  • Repository rules and the one default provider are gone: a workflow’s label picks a provider (runs-on: superci/provider=modal) and the order does the rest. Neither could be set for a long time. Updating a control plane that still has one says which, with the label that does the same.
  • Changes made at the same moment on several computers are all kept. The order, limits and launchers are kept by the control plane and written through it, each change to the one field it changes: a dialog’s change no longer writes back the fields it showed but did not change, over a teammate’s change to them. A field changed on another computer since the page showed it is refused, saying what it is now, with Set it anyway for that field alone; a command is taken as said. They were written into the cloud’s own settings whole, the last write winning. An older SuperCI’s change is still taken, as before. Update your control plane for it.
  • A Modal control plane makes every write from one container. Its sweep ran in a container of its own beside the one that answers requests, and an update ran the old one beside the new for a while: as Modal’s store cannot write over only what was read, two could take the same job, or lose a change. Now the minute’s schedule has the sweep run where the requests are answered, and an update stops the old container as the new one starts (requests meanwhile wait a few seconds). Jobs run in an app of their own (superci-jobs-<id>), so an update never stops them. Update your control plane for it.
  • A Modal control plane answers GitHub’s and GitLab’s events first and starts the job’s sandbox after, as an AWS one does: each of its reads and writes is a call to Modal’s API, and the event’s answer took most of the ten seconds GitHub waits before it counts a delivery as failed. Each write with its end is one call now, its Dict’s calls made side by side. Update your control plane for it.
  • A control plane’s status reads the newest jobs from one record, where a Modal or Cloudflare one listed every job of the last 90 days at each look; and what jobs are still going and the days’ totals once, not three times and twice. Update your control plane for it.
  • A Modal deploy works in any Modal workspace, however new: SuperCI tells Modal’s client which image builder version to build with (2026.10, with Modal’s client 1.6.3), where it took the workspace’s own, and a client refuses one newer than it knows. A workspace made now is on 2026.10, which SuperCI’s client before refused. By Taras Kornichuk (github.com/artile), who moved the client to 1.6.3. Update your control plane for it.
  • A Modal control plane or launcher deploys in a Modal workspace that has nothing of SuperCI’s yet. Modal had begun to refuse to create an app for a client whose version it could not read (“Could not determine the SDK version for client type CLIENT_TYPE_LIBMODAL_GO”), and SuperCI said its own: it now says Modal’s Go SDK’s, as that SDK does. By Taras Kornichuk (github.com/artile).
  • A Modal sign-in ends once it is approved in Modal’s tab, whatever the dashboard’s tab does meanwhile. Modal hands the token only to a call waiting at that moment: one now waits all the time. By Taras Kornichuk (github.com/artile).
  • What Modal says of a client release it will stop taking is said: by superci when it asks Modal, above the dashboard’s pages, and in superci status from the control plane, which keeps what its launchers and its own client heard. Update your control plane for it.
  • Updating the control plane updates its Modal launcher too (as it did a Cloudflare one), with a Modal sign-in to the workspace it is in: it kept the Modal client it was deployed with.
  • Modal Functions are a row of their own in the order, taken out until put in: superci runners order modal-functions modal (a further runner’s is WORD-functions). They are deployed when the row goes on. A Function costs a third of a sandbox ($0.0000131 a core-second and $0.00000222 a GiB-second, against $0.00003942 and $0.00000667), and jobs are priced so. Modal may preempt a Function and start it again: it then starts no runner (GitHub’s registration is used up) and says so, and the job is run again by itself further down the order once its run has finished, once at most. superci status and the dashboard count this month’s preemptions and the jobs run again. Its Functions, one per image, are deployed in that workspace when the row goes on, when an image is added or changed, and with superci runners create modal. Taking the row out goes back to sandboxes. Update your control plane, and a Modal launcher, for it. Asked for by Taras Kornichuk (github.com/artile).
  • A job on Modal can start from an image of your own, with a repository’s tools in it already: superci runner_images create rust-ci --reference=ghcr.io/acme/ci:2026-10, then runs-on: superci/image=rust-ci. A label is split at each /, so it names the image and the control plane keeps its address. Make the image FROM ghcr.io/actions/actions-runner; a job whose image has no GitHub runner, or one Modal cannot pull, fails at once, saying so. A private registry needs a Modal Secret (--modal-secret=NAME). A new build goes in under the same name in one change, so no job finds the name missing meanwhile: superci runner_images update rust-ci --reference=ghcr.io/acme/ci:2026-11. AWS and Cloudflare refuse such a job, saying why. Update your control plane, and a Modal launcher, for it.
  • A run from a computer whose workflow names actions/checkout by its commit (actions/checkout@3d3c42e…, as security guides advise) checks out the working tree as with a version (@v4). GitHub’s runner took its own copy of GitHub’s checkout, kept on the machine by that commit, which failed asking for a token. Update your control plane for it.
  • A run from a computer whose checkout names a full path inside the workspace (path: ${{ github.workspace }}/src/github.com/acme/app, as Go projects do) checks out there, as GitHub’s checkout does; one outside the workspace is refused, saying so. The full path was put under the workspace again, so the steps after found no checkout. Update your control plane for it.

0.19.21

· Release notes

  • A spot machine is asked for first among the pools near the cheapest in any of its regions, then in each region whole. When the first region had no room for the cheapest type, its dearer types were asked before the next region’s cheap one: a job whose label names family=c8a+m8a+r8a got r8a in N. Virginia at three times the price, and Ohio’s c8a was never asked. The first region still counts 15% cheaper. Update your control plane for it.

0.19.20

· Release notes

  • The spinner beside a step that takes more than one line (“Uploading the new functions (the control plane and its Docker image converter)”, in an update) stays round, beside the step’s first line. The step’s text squeezed it into an oval.
  • A job whose runner said it had ended, in a request the control plane could not finish (its store or a call failing midway), is ended when the runner says so again, and its machine stopped. It stayed running, its machine paid for until its time was up, because the runner’s second word said nothing new. The same for a runner saying it took its job. Update your control plane for it.
  • A GitHub job’s end that the control plane could not keep is kept when GitHub sends the event again. Its runner was forgotten before the end was kept, so the event sent again found no job. Update your control plane for it.
  • A job of a run from a computer whose start failed midway is started again by the control plane’s upkeep. It stayed “started” with nothing started, and the run never ended. Update your control plane for it.
  • A run from a computer refused when it is created leaves nothing behind. Its record was kept, and the upkeep started the run anyway after superci runs create had said it failed. Update your control plane for it.
  • A job’s cache or artifact is not lost to a passing failure: the control plane failing to read the job’s token for a moment (its store, or GitHub’s keys) is answered as a failure the machine asks again, not as a refusal it takes as final. Update your control plane for it.
  • A Docker layer a machine uploaded is kept when the control plane fails partway through taking it (its store, or S3 checking the upload): its record stays until the layer is being converted, and a conversion is noted before it is asked for. Such a layer was lost, or left “being converted” until it timed out, and the next job pulled it again. Update your control plane for it.
  • A command that names a control plane (--plane=ID) acts on it after another was in use in the same workspace. It was refused as “not among the control planes here” once a command had read the other one.
  • Removing AWS runners from a control plane that no longer knows any AWS account says it is done. It asked to sign in to an account with no number.
  • A job the control plane took as its store failed to index it is let go, to be taken again. It was left for nothing to look after. Update your control plane for it.
  • A control plane from before 0.19.0 building its jobs’ indexes a part at a time indexes the job each part ends at, and counts its run. That job was passed over. Update your control plane for it.
  • An AWS control plane reading many records at once while DynamoDB is busy reads every one of them. Records DynamoDB still left for later after eight tries were taken as not there: a job or a cache entry could look missing for that moment. Update your control plane for it.
  • A Cloudflare control plane reads its settings as the others do: the secrets kept for runs from a computer are listed and given to its runs, Settings lists each device’s key, and AWS runners turned off stay off. It read none of them. Update your control plane for it.
  • A Cloudflare runner whose container Cloudflare fails to stop says why, for the control plane to try again. It failed with an error Cloudflare’s runtime reported as uncaught. Update your control plane and its Cloudflare launcher for it.
  • A job on Modal ends as soon as its steps do, and a Modal control plane answers several requests side by side: a job whose steps take a second takes 5 seconds, where it took over 4 minutes, its machine paid for meanwhile. It answered one request at a time, and its runner’s asking for messages, the CLI following a run and the job’s own calls (its end too) each waited for the others. Update your control plane for it.
  • A Cloudflare launcher asked to start a runner in a place Cloudflare has no location for refuses it, saying so, and a Cloudflare control plane whose containers’ location is not one of Cloudflare’s starts them in eastern North America, as by default. Such a location went to Cloudflare as it was. Update your control plane and its Cloudflare launcher for it.
  • Setting up Cloudflare runners sends a chunk of the runner image that Cloudflare’s registry fails (a 500 of its own) again, twice. One such failure ended the setup.
  • A job whose spot machine AWS took back is not run again when its branch has a newer push whose run of the same workflow is still going. Run again, it came after that run, and a workflow that cancels runs in progress (concurrency with cancel-in-progress) cancelled the newer push’s run before any of its jobs began. Its page says why. Update your control plane for it.
  • Whether the GitHub App is installed is not kept while there is no App yet. A dashboard that asked before the App was made saw it not installed for a minute after it was. Update your control plane for it.