Skip to content

Release 1.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Sep 01:45
Immutable release. Only release title and notes can be modified.
bd0a4c2

Added

  • Added Dual-Format (Quick and Full) PROMPT.md guides across platform-builder, gitops-manager, and terraform-module-builder.
  • Added unit test suite in terraform-module-builder/scripts/tests/test_detect_migrations.py covering dynamic Git root discovery.
  • Added focused Terraform checker and documentation regressions, linked-worktree and submodule migration tests, and PR CI gates for the Terraform and platform Skill suites.

Changed

  • Aligned platform builder checks with tpl.container.image.repository auto-derivation in helm-tpl-library.
  • Implemented Clean Architecture Split: decoupled central skills and test suites from CI library templates.
  • Pinned repository CI reusable workflow callers to github-ci-library @1.3.1.
  • Clarified Terraform state-plan review and permitted apply only after a separate request and confirmation of the exact saved plan and target.

Fixed

  • Corrected Terraform checker false positives for sensitive outputs and minimum provider bounds; detect conditional governance-tag overrides.
  • Detect unreferenced Terraform data sources in any root-level module file.
  • Removed the migration detector's misleading clean/patch verdict for changes it cannot assess, including defaults and instance keys.
  • Corrected the state-migration guide's reference to procedures absent from the module library's current MIGRATION.md.
  • Corrected module documentation drift checks and stopped generating unverified security claims and relative-source examples for missing READMEs.

1.3.0

Terraform module interfaces require no consumer migration. Prompt scaffolds now feature Dual-Format options (Quick for streamlined pasting and Full for complete governance). Reusable workflows are pinned to @1.3.1. Terraform module work still stops after local validation by default; an explicitly requested apply now requires confirmation of the exact saved plan and target after review.

For a new module, write and review its README narrative and public release-tag examples before running generate-module-docs.py. The tool now updates only the generated tables in an existing README; it no longer creates a file with unverified security claims or a relative module source.