Merge branch 'main' into feat-ssm-runner-matcher-chunking

Author: npalm

CHANGELOG.md

@@ -1,5 +1,18 @@
 # Changelog
 
+## [6.8.0](https://github.com/github-aws-runners/terraform-aws-github-runner/compare/v6.7.9...v6.8.0) (2025-10-03)
+
+
+### Features
+
+* add cpu_options for EC2 launch template ([#4789](https://github.com/github-aws-runners/terraform-aws-github-runner/issues/4789)) ([20eeead](https://github.com/github-aws-runners/terraform-aws-github-runner/commit/20eeead48a4547e1f29257bbe771c14917d5db96))
+
+
+### Bug Fixes
+
+* **lambda:** bump the aws group across 1 directory with 7 updates ([#4805](https://github.com/github-aws-runners/terraform-aws-github-runner/issues/4805)) ([3025930](https://github.com/github-aws-runners/terraform-aws-github-runner/commit/3025930d4246c713285de2a314285e0d0881d4e1))
+* **lambda:** bump the octokit group in /lambdas with 3 updates ([#4794](https://github.com/github-aws-runners/terraform-aws-github-runner/issues/4794)) ([73cf01e](https://github.com/github-aws-runners/terraform-aws-github-runner/commit/73cf01e1652ece1e121295cbaab2ca22fe400e61))
+
 ## [6.7.9](https://github.com/github-aws-runners/terraform-aws-github-runner/compare/v6.7.8...v6.7.9) (2025-09-28)
 
 

docs/index.md

@@ -15,9 +15,9 @@ A pertinent question may arise: why not opt for Kubernetes? The current strategy
 
 ## Overview
 
-The module is designed to be used in a GitHub organization. It can also be used in a GitHub repository, but this does not supports all features. The module is receiving GitHub webhook events for the `workflow_job` event. The module will create a new runner if the event is for a workflow that requires a runner, and no runner is available. Alternatively the module can be configured as ephemeral runners. In this case the module will create a new runner for each workflow job event.
+The module is designed to be used in a GitHub organization. It can also be used in a GitHub repository, but this does not support all features. The module is receiving GitHub webhook events for the `workflow_job` event. The module will create a new runner if the event is for a workflow that requires a runner, and no runner is available. Alternatively the module can be configured as ephemeral runners. In this case the module will create a new runner for each workflow job event.
 
-For ephemeral runners a pool is can be configured. The pool maintains a minimum number of runners based on a schedule. The pool works only for org level runners.
+For ephemeral runners a pool can be configured. The pool maintains a minimum number of runners based on a schedule. The pool works only for org level runners.
 
 For non ephemeral runners with the idle config the module will avoid scaling down back to zero. Instead it will maintain a minimum number of runners based on a schedule. This avoids the need to scale up when a new workflow is triggered.
 

examples/default/main.tf

@@ -42,7 +42,7 @@ module "runners" {
   #   iops                  = null
   # }]
 
-  # When not explicitly set lambda zip files are grapped from the module requiring lambda build.
+  # When not explicitly set lambda zip files are grabbed from the module requiring lambda build.
   # Alternatively you can set the path to the lambda zip files here.
   #
   # For example grab zip files via lambda_download
@@ -68,7 +68,7 @@ module "runners" {
   # enable S3 versioning for runners S3 bucket
   # runner_binaries_s3_versioning = "Enabled"
 
-  # Uncommet idle config to have idle runners from 9 to 5 in time zone Amsterdam
+  # Uncomment idle config to have idle runners from 9 to 5 in time zone Amsterdam
   # idle_config = [{
   #   cron      = "* * 9-17 * * *"
   #   timeZone  = "Europe/Amsterdam"