github runs-on/runs-on v2.6.1

pre-release6 hours ago

New stack parameters and best practices compliance changes. No longer defaults to fetching global config when a local repo config is not found. Improve housekeeping to handle an additional AWS internal error case when launching an instance.

What's changed

  • Add parameter to enable/disable IPv6: Ipv6Enabled. Default is now false, which is a change from previous versions where IPv6 was always enabled. The reason for that is that it looks like docker pulls will go through IPv6 IPs, and for some reason they are getting rate-limited much faster than on IPv4. Will have to dig a bit deeper into that. Fixes #177.
  • Add parameter to disable the inbound SSH rule in the default security group for runners: SSHAllowed. Default is true. Fixes #174. Fixes #159.
  • Add VpcFlowLogRetentionInDays stack parameter. Fixes #180.
  • No longer defaults to fetching global config when a local repo config is not found. The current behaviour was a bit broken with the caching mechanism, and lead to confusion. Let's make the behaviour explicit by requiring a local repo config file, with an explicit _extends directive. I understand this is a bit cumbersome if you have many repositories, but I think it's also nice to be able to inspect which repositories are inheriting from the global config. I'm introducing this change as part of a patch release because the current behaviour was already broken on v2.6.0.
  • Housekeeping: Detect AWS server issue that sometimes leaves instances in pending state, in which case RunsOn will terminate the current instance, and reschedule.
  • Enable versioning on all S3 buckets. Fixes #181.

Upgrade

Don't miss a new runs-on release

NewReleases is sending notifications on new releases.