ArticlesJuly 7, 2026

Available Versions

Created: March 9, 2026
Updated: July 8, 2026

This resource is the concise version inventory for Cloud Ops Works Blueprints, application templates, project templates, and repo-management modules. Detailed rollout guidance now lives in dedicated resources, so this page stays focused on what version is available and which repository provides it.

Blueprint & Language Versions

Blueprint references inside generated workflows are intentionally pinned by major/minor channel, such as @v5.10, while the released Blueprint repository still publishes patch tags. The table below separates the Blueprint channels from template release lines: each Blueprint column shows the latest template tag whose workflows are aligned to that channel, and N/A means that area does not have a released implementation for that Blueprint channel.

Areav5.8 Blueprintv5.9 Blueprintv5.10 BlueprintLatest VersionDefault RuntimeVersion NotesRepository
CloudOpsWorks Blueprintsv5.8.19 (deprecated)v5.9.97v5.10.73v5.10.73GitHub ActionsBlueprint repository publishes all supported channels; generated workflows should pin the major/minor channel rather than chase patch tags.blueprints
Javav5.7.4v5.8.31v5.9.33v5.9.33JDK 25Adds Conventional Commits Ruleset toggles and Terraform CI template mapping.java-app-template
NodeJSv5.7.4v5.8.31v5.9.30v5.9.30Node 24Adds S3 static-hosting deployment inputs with optional CloudFront invalidation settings.node-app-template
Pythonv1.2.4v1.3.37v1.4.25v1.4.25Python 3.14Adds safe-default Ruleset settings with YAML-safe custom regex rendering and Terraform fallback support.python-app-template
Xcodev5.2.0v5.2.1v5.3.20v5.3.20Xcode 16.4Adds safe-default Ruleset settings with YAML-safe custom regex rendering and Terraform fallback support.xcode-app-template
Gov1.1.1v1.2.14v1.3.36v1.3.36Go 1.25Adds branch-protection, Conventional Commits Ruleset, enforcement, and custom pattern template variables.go-app-template
.Netv1.1.1v1.2.15v1.3.24v1.3.24.NET 10.0Adds Ruleset governance keys and Terraform template parameterization for branch/enforcement settings.dotnet-app-template
Rustv0.1.1v1.1.1v1.2.21v1.2.21Rust stableAdds safe-default Ruleset settings with YAML-safe custom regex rendering and Terraform fallback support.rust-app-template
Android SDKN/AN/Av1.0.16v1.0.16Android SDK 16.0Adds Conventional Commits governance settings and Terraform template mapping.androidsdk-app-template
Flutter MobileN/AN/Av1.0.21v1.0.21Flutter stable, Android SDK 16.0, Xcode 16.4Adds Conventional Commits Ruleset options to rendered and Terraform CI configs.fluttermobile-app-template
Docker (plain)v5.8.0v5.9.0v5.10.23v5.10.23node:18-alpineAdds commit-message Ruleset governance entries and Terraform template parameterization.docker-app-template
Terraform ProjectN/AN/AN/Av3.0.4Terraform / OpenTofuAdds cloudopsworks-ci.yaml.tftpl for repo-management rendering from generated repositories.terraform-project-template
Terragrunt Projectv1.8.9v1.8.29v1.9.33v1.9.33Terragrunt / OpenTofuDisables implementation issue forms at template level while preserving implementation-copy behavior.terragrunt-project-template
Terraform Module TemplateN/AN/Av1.6.39v1.6.39Terraform / OpenTofuDisables explicit Checkov source_ref override so checkout uses the default workflow ref.terraform-module-template
GitHub Repo Management ModuleN/AN/Av1.4.7v1.4.7Terraform / GitHub providerMoves Conventional Commits validation settings into the generated CI/CD branch/enforce configuration model.terraform-module-github-repo-management

Latest Blueprint Highlights

  • Use Blueprint @v5.10 for the active workflow channel; its latest published patch is v5.10.73.
  • Use Blueprint @v5.9 only for repositories that still need the maintained previous channel; its latest published patch is v5.9.97.
  • Blueprint v5.8 is deprecated. The @v5.8 channel is listed only for historical/deprecation visibility; its latest published patch is v5.8.19.
  • The Blueprint columns list the latest template release detected for each workflow channel, not previous patch releases within a template's own version line.
  • Template releases keep new governance settings disabled by default, so upgrading a template does not immediately block commits.
  • Terraform template variants expose branch protection and commit-message policy settings through branch.* and enforce.* variables.
  • For the plain-language rollout guide, see Branch Protection Rulesets for Conventional Commits.

Important Notes

  • Prefer the newest template releases listed above when creating or upgrading repositories.
  • Keep cloudopsworks-ci.yaml and cloudopsworks-ci.yaml.tftpl together in template repositories.
  • Start Ruleset rollout in evaluate mode before enabling blocking enforcement.
  • Blueprint v5.8 is deprecated. Prefer @v5.9 only for repositories that cannot yet move to @v5.10; otherwise use the active @v5.10 channel.
  • Blueprint v5.10 includes an important API Gateway deployment change from earlier release waves. Coordinate migrations before upgrading older API Gateway deployments.
  • When upgrading older generated repositories, include the original Blueprint version used to create them to avoid accidental drift.

Upgrade Commands

Use either the repository Make targets or the Tronador CLI commands to manage template upgrades:

GoalMake targetTronador CLI
Show available template versions before modifying files.make repos/availabletronador repos available --workdir ../my-service
Upgrade to the latest compatible patch within the same minor line.make repos/upgradetronador repos upgrade --workdir ../my-service
Jump to the latest compatible version within the current major line.make repos/upgrade/majortronador repos upgrade major --workdir ../my-service
Upgrade to a specific tag or branch, recommended when a repository is older than the currently supported baseline.make repos/upgrade/vX.Y.Ztronador repos upgrade vX.Y.Z --workdir ../my-service
Upgrade from the template repository master branch tip. Use only when explicitly tracking unreleased template state.make repos/upgrade/mastertronador repos upgrade master --workdir ../my-service

When you are already inside the target repository, omit --workdir ../my-service.

Ready to Standardize Your Cloud Operations?

Stop reinventing the wheel. Partner with Cloud Ops Works to build the engineering foundations your team needs to scale reliably.