v2.7.0 - Changelog

Summary

A few minor breaking changes related to VPC flow logs and hdd label. Plus many fixes.

Breaking changes

This is a minor release, so this comes with the following breaking changes. Please review your CloudFormation parameters and runner configuration accordingly when updating:

Fix for #258. VPC Flow Logs are now only enabled if the VpcFlowLogFormat is set to a non-empty value. To enable, and use the default format (as it were before if you didn't specify a value), specify default.
Remove support for the deprecated hdd job label. Ensure all your workflows and repository configuration (.github/runs-on.yml) do not use this label. If it is still set, it will have no effect and the default runner configuration will be used for disk sizing. You must now use the disk=default or disk=large label instead.

What's changed

Fix for S3 server access logging. Fixes #241.
Allows specifying the root volume name. Fixes #207.
Expose RUNS_ON_AWS_AZ and RUNS_ON_INSTANCE_LAUNCHED_AT environment variables to jobs.
Properly set RUNNER_TOOL_CACHE 🤦, so that some setup-* actions can properly use the hosted toolcache on the VM.
Add policy to allow instances to describe their tags. Means we no longer need to enable InstanceMetadataTags for the instances. Cost Allocation Tag and Runner Tags can now contain slashes in their keys.
Add runs_on_spot_circuit_breaker_active prometheus metric (1=active, 0=inactive). Fixes #271.
Ensure we don't try to auto-retry after spot termination if the workflow run has already been manually re-attempted. Fixes #263.
Fixes typo - Fixes #248.
Scope the minutes alarm on the stack name. Also add the StackName dimension on all metrics. Fixes #235.
(alpha, not fully functional yet) Support for GitHub Enterprise Server (GHES) installations.