Available Versions

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

This document provides an overview of the currently available versions for our Blueprints and various programming languages and SDKs. It also captures the latest template metadata patch wave, Flutter mobile template field notes from OMX activity, and how the templates work with the Tronador DevOps accelerator.

Blueprint & Language Versions

The following table summarizes the supported versions across different Blueprints and template repositories:

Latest Blueprint Highlights

• The June 8, 2026 template patch wave added cloudopsworks-ci.yaml.tftpl beside the rendered CI/CD config in every active application template, plus the Terraform project template.
• terraform-module-github-repo-management can now read the template source from newly created repositories and render replacements without carrying language-specific .tftpl copies in the module.
• The rendered cloudopsworks-ci.yaml remains in each template so direct template users keep the same first-clone experience.
• Java, NodeJS, Python, .NET, Docker, Xcode, Android SDK, Go, Rust, Flutter Mobile, and Terraform Project templates all received patch-only releases for this metadata move.
• Shared cloudopsworks/blueprints support remains on the v5.10 channel, with the latest observed channel tag at v5.10.68.

Current Open Source Repository Rotation

Terraform Modules

The current public module rotation keeps at least six actively maintained Terraform modules visible and favors recently updated repositories:

• terraform-module-mongoatlas-aws-users — MongoDB Atlas users with AWS Secrets Manager and Lambda rotation dependencies.
• terraform-module-mongoatlas-users — MongoDB Atlas user management.
• terraform-module-aws-secrets-rotation-lambda-setup — AWS Secrets Manager rotation Lambda setup aligned to database management modules.
• terraform-module-aws-alb-certificate-management — Application Load Balancer certificate management.
• terraform-module-gcp-cloud-storage — GCP Cloud Storage buckets with versioning, lifecycle, encryption, logging, and IAM policies.
• terraform-module-github-org-management — GitHub organization management.
• terraform-module-gcp-mysql-management — GCP Cloud SQL MySQL databases and users with Secret Manager credential storage.
• terraform-module-aws-mysql-management — AWS MySQL and MariaDB database/user management with Secrets Manager and Hoop.dev integration.

GitHub Actions

Archived actions have been removed from the active list. The maintained action rotation keeps no fewer than three entries:

• changelog-action — maintained conventional commit changelog action.
• actions-runner — specialized GitHub Actions runner for Cloud Ops Works Blueprint pipelines.
• github-action-jira-release — creates Jira releases that synchronize with GitHub releases.
• github-action-next-semvers — outputs next major, minor, and patch versions from a semver input.

Important Notes

• Recommendation: Prefer the newest template releases listed above when creating or upgrading repositories. The newer versions include CI template source metadata for repo-management rendering while preserving rendered defaults for direct template users.
• Breaking Changes: Blueprint v5.10 includes an important API Gateway deployment change. Coordinate migrations before upgrading older API Gateway deployments.
• GitHub Repo Management: Keep cloudopsworks-ci.yaml and cloudopsworks-ci.yaml.tftpl together in template repositories. Repo-management can render generated repository CI/CD configuration from the template source stored in the new repository.
• Flutter Mobile: Use the v5.10 blueprint channel with fluttermobile-app-template v1.0.20 or newer so Flutter fixes and template metadata updates can be consumed without pinning every workflow to a patch-specific blueprint tag.
• Upgrading: When upgrading older generated repositories, include the original Blueprint version used to create them to avoid accidental drift.

Upgrade Commands

Use the following commands to manage your version upgrades:

• make repos/upgrade: Continues to work the same way, but upgrades patch versions.
• make repos/upgrade/major: Used to jump to the latest major version.
• make repos/upgrade/vX.Y.Z: Used to upgrade to a specific version, recommended when a repository is older than the currently supported baseline.