Skip to content

Changelog

About RunsOn

Versions

v2.5.4

New ubuntu24 images, new housekeeping task, new always-on Private setting, additional runner details in logs, and more.

v2.5.2

Summary: refactor rate-limits, fix housekeeping behaviour, add missing cost allocation tags, fix rare preinstall bug, unregister runner from github after job termination.

v2.5.1

New ubuntu24 images, additional runner details in logs, scheduling retry mechanism if internal AWS server error when launching, and more.

Note: DO NOT USE this release. The new housekeeping behaviour is not working as expected.

v2.5.0

Summary: Allow to assign an environment name to each RunsOn stack. Allow to specify VPC CIDR block and export outputs to facilitate VPC peering connections. Allow to set custom tags on instances.

v2.4.0

Summary: beta windows support, prometheus metrics, disk statistics in workflow logs.

v2.3.2

Summary: a fix for useless creation of instances when hitting quota errors, reverting the unbounded cpu and ram change (from v2.3.0), and CloudWatch agent now streams instance logs into CloudWatch.

v2.3.1

Summary: Auto-mounting of ephemeral disks, improvements in dangling instance cleanup, better handling of preinstall.

v2.3.0

Summary: Allow setting custom spot allocation strategy, cpu and ram behaviour change, config file is now read from the current branch for private repositories. And 2 new regions!

v2.2.4

Summary: properly handle jobs with environments attached.

Note: this newer version requires a permission update for the accompanying GitHub app. You will receive an email after the upgrade with instructions on how to make the change. If you do nothing, RunsOn will still work, but the fix below will not be active.

v2.2.3

Summary: make volume network throughput configurable, reduce alert noise for spot quota exceeded. And 1 new region!

v2.2.2

Summary: Add more tags to EC2 instances, and many fixes. Plus 2 new regions!

v2.2.1

Summary: fix _extends handling in config file.

v2.2.0

Summary: Private subnet support, new retry mechanism, spot interruption detection, bare-metal support, and many fixes and improvements.

v2.1.0

Summary: full rewrite in Go, use external FIFO queue to keep jobs in flight.

v2.0.13

Summary: switch to CreateFleet API, multi-az support, multi-region support + many fixes.

Warning: this is a major release bump, with a new VPC being created. You are advised to upgrade either during a quiet time (no runner running, otherwise the old VPC cannot be destroyed), or simply create a new stack with that template, follow the configuration process, and then Pause the previous AppRunner service until you validate that everything is going fine. Doing it this way will allow you to easily roll back to the previous version by just removing the new stack and clicking Resume on the previous AppRunner service.

v1.7.4

Summary: handle conflict when registering runner.

v1.7.3

Summary: Reduce rate-limit issues, add m7i as additional family type for default runners. Plus 2 new regions!

v1.7.2

Summary: IMDSv2 support, instant reload after first setup, add tags on instance and publish metrics.

v1.6.5

Summary: better error message when trying to launch EC2 instance.

v1.6.4

Summary: fix race-condition when updating the stack.

v1.6.3

Summary: Fix error message when unable to launch a runner.

v1.6.2

Summary: avoid EC2 rate-limit issues.

v1.6.1

Summary: Support for S3 backend for storing caches. New ubuntu22-full-arm64 image.

v1.5.0

Summary: Faster boot times, proper disk resizing, new licenses, better surfacing of internal timings right into the job log output.

v1.4.2

Summary: Allow overriding SSH admin selection

v1.4.1

Summary: Fix instance selection.

v1.4.0

Summary: Send cost report and alerts via email, instead of GitHub issue. Add S3 gateway. And many fixes.

v1.3.8

First official release πŸŽ‰