Skip to content

Releases

Release 4.1.0

Choose a tag to compare

@github-actions github-actions released this 16 Nov 10:47
Immutable release. Only release title and notes can be modified.
47f0415

Added

  • platform-builder: audit check in GitLab CI adapter for extraneous root VERSION files (Extraneous VERSION File). In GitLab CI, projects declare semantic versions via RELEASE_VERSION under variables: in .gitlab-ci.yml or in Chart.yaml.
  • platform-builder: audit checks for enterprise base image ARG defaults (Enterprise Base Image Tag and Unnecessary Renovate Annotation). Enterprise base images default to :latest for local developer builds and manage versions through CI library updates without Renovate.

Changed

  • platform-builder: _is_public_image recognizes TRUSTED_INTERNAL_REGISTRIES (grootantech/*) so Renovate annotations are not requested on internal/enterprise base images.
  • platform-builder: documentation in SKILL.md clarifies base image :latest default rules and GitLab CI RELEASE_VERSION vs GitHub Actions root VERSION file usage.

4.1.0

No migration is required. This release adds audit checks for Dockerfile enterprise base image defaults and GitLab CI versioning declarations.

Release 4.0.0

Choose a tag to compare

@github-actions github-actions released this 13 Nov 11:00
Immutable release. Only release title and notes can be modified.
6bd42a8

Changed

4.0.0

No migration is required. This release only updates dependencies.

Release 3.0.0

Choose a tag to compare

@github-actions github-actions released this 05 Nov 05:33
Immutable release. Only release title and notes can be modified.
854133c

Added

  • observability-builder: every attribute, field and label now has a class per location — mandatory, conditional, recommended, optional or prohibited — with who sets it and when (references/data-model.md). The tables cover the resource per platform, trace context, request and identity context, operation spans, logs, metrics, profiles, correlation and AI (GenAI, agents, RAG, MCP, A2A). Maintainer notes on the design are in docs/attribute-standard-design.md.
  • observability-builder: platforms outside Kubernetes: ECS and Fargate, Lambda, Cloud Run services and jobs, VMs and plain Docker, each with its own required resource rows and instance identity, set by platform detectors with a short start-up timeout.
  • observability-builder: A2A (agent-to-agent) calls: workloads/a2a.md, the invoke_agent client span and server entry span, app.a2a.* attributes, traceparent on the JSON-RPC call, and the a2a_client_request_duration_seconds / a2a_server_request_duration_seconds metrics.
  • observability-builder: a shared masking helper for personal data in logs, span attributes and exception messages (emails, phones, names, addresses, government and bank IDs, dates of birth, IPs outside the access and audit logs); it fails closed. A new audit log kind (audit.<action>).
  • observability-builder: references/overhead-and-security.md and scripts/overhead.py: instrumentation must stay within an overhead budget (latency, CPU, memory, errors, shutdown), measured with telemetry on and off, and must not weaken security (TLS off private hops, credentials from files, metrics and profiling ports bound no wider than the scraper needs, packaged config, pinned dependencies). Overhead testing is now part of acceptance.
  • observability-builder: scripts/receiver/conformance.py checks captured telemetry against the data model (receive.py --platform, conformance.json). New audit rules: identity-from-header, request-id-attribute, code-namespace, pii-unmasked, profile-label-mismatch, baggage-over-limit, resource-excluded-key, sync-exporter, exporter-no-timeout, plaintext-remote-endpoint, telemetry-credential-literal, metrics-public-bind, attribute-limit-raised, log-extras-passthrough, eager-debug-format.
  • observability-builder: browser RUM with Grafana Faro for single-page apps (spa workload) and the page side of fullstack apps (references/signals/rum.md, workloads/spa.md). Every self-hosted Faro feature is on: errors, console, web vitals with attribution, performance and resource timing, sessions, views, soft navigation, user actions, frustration, CSP violations, custom signals, browser-to-API tracing and React. Three transports: direct to a public Alloy faro.receiver (default), a same-origin proxy (instrument always asks whether it is needed), or the experimental OTLP transport. Faro starts from runtime config without blocking the render, and every item passes a fail-closed beforeSend scrubber. The rum key returns to observability.yml with this new shape, and the release adds tested templates in assets/js/faro, a Grafana dashboard covering every field Faro sends (68 panels, each query checked against live data), the faro.receiver collector block, RUM queries for Loki and Tempo, and a browser overhead budget with scripts/rum_overhead.mjs. The receiver takes Faro batches on /collect and checks them against the data model. Twelve faro-* audit rules and rum-access-log-query were added. Everything was tested end to end on Alloy 1.21, Loki 3.7 and Tempo 3.1.
  • observability-builder: new conditional metrics for RPC (rpc_server/client_duration_seconds), messaging (messaging_process_duration_seconds, messaging_messages_total) and authentication (auth_attempts_total).

Changed

  • observability-builder: the resource keeps the SDK, runtime and OS rows (telemetry.sdk.language/version, process.runtime.*, os.type) and no longer carries k8s.pod.uid; service.instance.id, process IDs and command lines, vcs.*, host.id and deployment.id are never added. The collector matches pods by namespace and pod name, then IP, and adds the owning workload's name.
  • observability-builder: identity comes only from trusted middleware after authentication, never from raw client headers; request.id is not used. Identity rows beyond the core set are added only when the service's code has the value.
  • observability-builder: baggage is limited to an allow-list of at most 8 keys and 512 bytes; exception span events are not added (the error log record carries the exception); gen_ai.usage.cost is no longer allowed on the ops path; the GenAI token type cache_write is now cache_creation.
  • observability-builder: the Langfuse exporter templates (Go, Java, TypeScript) cap each request at 3 MiB by default and cap content in linear time; hold_port.py now holds a port reliably on macOS; audit.py --module accepts absolute paths and no longer flags the skill's own scripts or filtered detectors.
  • observability-builder: the Python module's logging file is logs.py, since logging.py shadows the standard library.
  • observability-builder: genai.content.max_chars defaults to 8000 and stays at or below the span attribute value limit (8192 by default), so the content cap runs before the SDK cuts anything; longer content raises both together as a recorded exception.
  • observability-builder: request context (client address, user agent, headers, cookies, query strings, peer addresses) never goes to Langfuse: the exporter templates and the collector's Langfuse branch drop it in every content mode. The TypeScript Langfuse transport sends OTLP/protobuf, and Langfuse export failures are logged as rate-limited WARN.
  • observability-builder: the overhead budget also accepts up to 1 ms of added CPU per request (cpu_ms_per_request); a function span for an exception that maps to a 4xx response stays UNSET; tracers, meters and loggers are obtained once; Python metrics servers don't reuse a taken port.
  • observability-builder: AI spans on the ops path no longer get user.id and team.id from the feature stamps; request identity stays on the entry span, and Langfuse keeps the user and team in its own trace context. AI spans keep gen_ai.conversation.id, and spans that aren't AI calls still lose stray gen_ai.*, llm.* and traceloop.* keys. The collector's GenAI routing drops content on the ops branch unconditionally.
  • observability-builder: generated correlation ids are URL-safe base64, not hex (hex can look like a card number); a Python metrics server that can't bind without reuse retries with reuse when no listener answers (restarts after a scrape); Python allocation profiling (pyroscope-io 1.3+) is allowed after the overhead test; AI content is passed to the content helper as a function, so nothing is converted while capture is off.
  • observability-builder: detect.py reports a project that is only pages as workload spa, sets frontend for fullstack apps, and lists browser RUM SDKs (Faro, Datadog, New Relic, Elastic, Dynatrace, Application Insights, Splunk, OpenTelemetry Web) as existing telemetry.
  • platform-builder: the example product in docs and tests is storefront instead of oneuptime.

Removed

  • observability-builder: OneUptime as a backend: backends/oneuptime.md, its collector exporter and identity stamping, and the OneUptime examples in the other pages. The Grafana stack, Dynatrace, New Relic, AWS and Langfuse remain (see MIGRATION.md).
  • observability-builder: the OneUptime browser RUM (OpenTelemetry Web SDK) and session replay, with its rum key shape, the receiver's session-replay stand-in and --replay-assets, and the rum-propagate-all and rum-input-capture audit rules. Browser RUM is now Grafana Faro (see Added).
  • observability-builder: genai.content.destination and the receiver's --genai-content-destination. AI content goes to Langfuse only, never to the ops backend.

3.0.0

Required

  • Resource attributes. Remove k8s.pod.uid, service.instance.id, process.pid, process.command_line, process.executable.*, vcs.*, host.id and deployment.id from observability.yml and from code; the schema now rejects them. Stop dropping telemetry.sdk.language/version, process.runtime.* and os.type. Remove the pod UID from the chart's downward API, and update collectors to the pod association in observability-builder/references/collector/README.md (namespace and pod name, then IP; workload names extracted).
  • Identity. Services that set user.id or tenant.id from client headers must take them from the authentication or tenant middleware instead. Remove request.id; use correlation.id.
  • Metrics. Rename the GenAI token_type value cache_write to cache_creation in code and dashboards.
  • GenAI content size. genai.content.max_chars now defaults to 8000. A yml that sets a larger value must also set the span attribute value limit to the same number, with a comment naming max_chars, or lower it to 8192 or less.
  • Collectors with GenAI routing: add the langfuse_request_context transform from observability-builder/references/collector/README.md before the Langfuse batch.
  • OneUptime is no longer a supported backend. Point each service's telemetry at a remaining
    backend (the Grafana stack, Dynatrace, New Relic or AWS) by changing only observability.yml
    and the collector configuration (backends):
    • remove the OneUptime exporter, its x-oneuptime-token auth and the
      deployment.environment transform from collectors;
    • remove x-oneuptime-token headers and oneuptime.label.* resource attributes from
      observability.yml and from the chart's resource.opentelemetry.io/* annotations;
    • remove oneuptime.database.server.id stamping from database-engine pipelines.
  • **De...
Read more

Release 2.0.0

Choose a tag to compare

@github-actions github-actions released this 31 Oct 22:42
Immutable release. Only release title and notes can be modified.
3e9db15

Release 2.0.0

Release 1.8.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 21:43
Immutable release. Only release title and notes can be modified.
7400e47

Added

  • Every library-backed skill reads a library at the release the project pins and, for a new project or an upgrade, at the library's latest release tag. platform-builder finds the pin in the GitLab includes, the GitHub reusable workflows and the chart's tpl-library dependency, gitops-manager in the environment's root and extras/Chart.yaml. libraries.py and audit.py take --latest for an upgrade, which platform update uses. A library release needs no skill release.
  • platform-builder: the checks read their library rules from the data file that release ships, docs/workflow-map.json of the CI library and docs/chart-contract.json of helm-tpl-library; chart-docs.sh takes its helm-docs flags from the contract of the chart's own dependency. A release without the file, or with a schema the skill does not know, stops the run before any check and says what to upgrade.
  • platform-builder: a "Mixed Library Pins" finding when includes or workflows pin different releases of one library; the run reads the oldest.
  • platform-builder: Terraform repository detection. A repository with *.tf files at its root and no application manifest, Dockerfile or chart audits as the terraform shape; before, it was unrecognised and no shape check ran on it.
  • gitops-manager: app_add.py takes the Application name, namespace and release name from helm template of the library release the environment pins, and the values-file path, sync presets and release-shape keys from its docs/environment-map.json. override_check.py takes what an environment may override from the same map, and the service library's root keys from the tpl-library release the service chart pins.

Changed

  • CI calls the github-ci-library 1.7.0 reusable workflows instead of 1.5.0.
  • COMPATIBILITY.md lists no library releases; it says how the skills choose a release and that each library's README and MIGRATION.md own its versions, requirements and upgrades. The README carries no release number, and the install commands check out the newest tag.
  • platform-builder, gitops-manager: the bundled workflow maps and the copies of the libraries' chart, naming and override rules are gone; the entry files point at the libraries' docs instead of restating them, and a test keeps versions and release claims out of them.
  • platform-builder: the migration chain takes the release list from the library's remote, so a shallow clone no longer drops the releases between the pin and the target, and a pre-release is not counted as a release.

Removed

  • platform-builder: chart rules the library does not have: the myorg and [PRODUCT_NAME] placeholders, the parity exception for component and subComponent, the configmapEnvs @default rule and values-*.yaml overlays.

Fixed

  • platform-builder: "Chart Image Differs From CI Push Path" no longer reports a correct chart when IMAGE_REPOSITORY lists several repositories, or full repositories for a credential group; the chart may pull from any listed one.
  • platform-builder: the base-image and dependency-cache guidance points at the selected CI library's Dockerfile standards instead of naming images and library behaviour that change with its releases.
  • observability-builder: the skill version comes from the ai-skills release, not from a README line that was not kept up to date.

1.8.0

Required

  • Libraries are read at a release, not at main. A skill reads each library at the
    release the project pins, or at the latest release tag for a new project or an upgrade
    (platform update, audit.py --latest). To read another ref, name it: a --<library>
    source, $PLATFORM_BUILDER_LIB_<NAME> or .platform-builder.json.
  • The libraries' data files are required. The checks read their rules from the data file
    a library release ships. A project pinned to an older release stops with the release to
    upgrade to: run platform update first, or stay on ai-skills 1.7.0 until then.
  • COMPATIBILITY.md no longer lists library releases. The 1.4.0 rule that a library pin
    be at least the listed release is gone: pin any release, and the skill reads that release.

Recommended

  • Remove ref: main from a .platform-builder.json that only pinned it to follow the
    libraries: the project's own pins now decide.
  • gitops-manager needs helm to add a service: it renders the pinned library to name the new
    Application.

Verify

  • python3 -m unittest discover -s platform-builder/core/scripts/tests passes, and so do the
    gitops-manager, terraform-module-builder and observability-builder suites.
  • audit.py prints each library with via project pin or the latest release, and a project
    on a release without the data file stops with exit code 2 and the release to upgrade to.

Release 1.7.0

Choose a tag to compare

@github-actions github-actions released this 23 Oct 16:03
Immutable release. Only release title and notes can be modified.
e81eb97

Changed

1.7.0

No migration is required. This release only updates dependencies.

Release 1.6.0

Choose a tag to compare

@github-actions github-actions released this 14 Oct 16:17
Immutable release. Only release title and notes can be modified.
6be1827

Added

  • observability-builder: OneUptime's AI / LLM views as an LLM-monitoring destination. genai.content.destination (langfuse or ops) sends prompts and answers to one tool per service, never both, and backends/oneuptime.md describes what the views read: call kinds, problems, conversations, usage and pricing.
  • observability-builder: who spent what. The spender, the team and the conversation come from the app's own verified context, decided per entry point; on the ops path AI spans carry user.id, team.id and gen_ai.conversation.id, where OneUptime attributes spend.
  • observability-builder: MCP servers and clients (workloads/mcp.md): a span per message on each side, context through params._meta, the JSON-RPC status rules, one span per tool call, and the mcp_server_operation_duration_seconds and mcp_client_operation_duration_seconds metrics.
  • observability-builder: the genai-langfuse-two-senders audit rule; validate checks for the content destination; the receiver's --genai-content-destination flag and summary lines for who spent what, AI keys on other spans, retrieval steps, MCP and Langfuse span senders.

Changed

  • observability-builder: retrieval steps carry gen_ai.operation.name=retrieval and gen_ai.retrieval.top_k; memory, planning and agent-creation step kinds are added; a sub-agent call is one invoke_agent span; the turn's input and output go on the Langfuse trace; no cost is written unless the provider reports one.
  • observability-builder: the ops allow-list keeps the MCP keys, the OpenInference and OpenLLMetry model and usage keys, and user.id and team.id; spans that aren't AI calls lose their gen_ai.*, llm.* and traceloop.* keys, which OneUptime would count as AI calls. The collector's GenAI routing does the same.
  • observability-builder: one span sender to Langfuse per service is a stated rule; all three Langfuse modes stay, with hybrid the default.
  • observability-builder: SDK notes for openai 3 and mcp 2 over httpx2, the MCP Python SDK 2.x client spans and protocol probe, OTLP exporter errors fed back into the log export, ExceptionGroup on FastAPI SERVER spans and the JavaScript exporters' warning on JSON replies. Direct export to OneUptime: ops metrics need a scraper, and the yml adds deployment.environment for exceptions. Path exclusions are decided when the response ends.
  • README and COMPATIBILITY list the 1.6.0 release.

1.6.0

Required

No migration required. genai.content.destination defaults to langfuse, the 1.5.0 behaviour,
so existing observability.yml files validate and behave unchanged.

Recommended

  • Re-run observability instrument on services that call a model, to add the user, team and
    conversation to their AI spans (OneUptime's Usage shows their spend as Unattributed without
    them), the retrieval operation, the new allow-list keys, and the removal of AI keys from spans
    that aren't AI calls.
  • Where prompts and answers should be read in OneUptime instead of Langfuse, set
    genai.content.destination: ops, with Langfuse mode hybrid or otel, or Langfuse off.
  • Instrument MCP servers and clients with references/workloads/mcp.md, including the server
    and client MCP metrics.
  • Collectors with GenAI routing: update the ops branch from references/collector/README.md
    (identity on AI spans, AI keys off other spans, the new allow-list) and list the services whose
    content destination is ops in both branches (^$ while there are none).
  • Services exporting straight to OneUptime: add deployment.environment: "${OBS_ENVIRONMENT}"
    under resource.attributes, arrange a scraper for /metrics, and add OneUptime prices for
    self-hosted or aliased models.

Verify

  • python3 -m unittest discover -s observability-builder/scripts/tests passes, and the receiver
    tests pass with uv run --no-project --with grpcio --with opentelemetry-proto --with protobuf --with pyyaml python -m unittest discover -s scripts/tests -p "test_receive.py" from
    observability-builder/.
  • A re-instrumented AI service's receiver summary shows the user, team and conversation on its AI
    calls and no AI KEYS ON OTHER SPANS alarm.

Release 1.5.0

Choose a tag to compare

@github-actions github-actions released this 10 Oct 05:22
Immutable release. Only release title and notes can be modified.
33ba329

Added

  • observability-builder: instruments any service or frontend for end-to-end observability from one observability.yml — access logs, structured application logs, OpenTelemetry traces with nested function spans, ops metrics on a Prometheus /metrics port, error logs, Pyroscope profiling, browser RUM and session replay, and LLM and agent telemetry with Langfuse — and audits existing telemetry for unsafe capture. Two workflows: observability instrument (detect, ask, audit, research, plan, implement, verify against a real receiver, report) and observability audit.
  • observability-builder: the observability standard it applies, bundled in references/ (signals, workloads, backends, collector, data model, safe capture, SDK notes), and the observability.yml JSON Schema in assets/.
  • observability-builder: detect.py, validate.py, audit.py, contract.py and hold_port.py; receive.py, a local OTLP, Pyroscope and session-replay receiver with a Langfuse stand-in and canary tracking; llm_stub.py, an OpenAI- and Anthropic-compatible model stub, so verification never calls a real provider.
  • observability-builder: Langfuse export, content-guard and score pieces for Node.js, Go and Java, and the Java JFR-to-pprof profile exporter.
  • observability-builder: PROMPT.md and script regression tests.

Changed

  • Pinned the repository's reusable workflow callers to github-ci-library @1.5.0.
  • PR verification runs the observability-builder script tests.
  • README and COMPATIBILITY list the 1.5.0 release set and the new skill; observability-builder bundles its standard instead of reading a library.

1.5.0

Required

No migration required. This release adds the observability-builder skill; no existing skill
changed, and the reusable workflow pin moves to github-ci-library 1.5.0, whose inputs,
outputs and behaviour are unchanged.

Recommended

  • Install the new skill where services need observability work:

    npx skills add https://github.com/grootan-devops/ai-skills \
      --skill observability-builder
  • Its scripts need Python 3.10 or newer with PyYAML. The local receiver also needs grpcio,
    protobuf and opentelemetry-proto, which uv run --no-project --with … supplies, as the
    skill's README shows.

  • observability-builder bundles its standard in its own references/ and assets/; it reads
    no library and needs no entry in .platform-builder.json.

Verify

  • python3 -m unittest discover -s observability-builder/scripts/tests passes (the receiver
    tests skip themselves without grpcio).
  • The pull request pipeline passes with the 1.5.0 library pin.

Release 1.4.0

Choose a tag to compare

@github-actions github-actions released this 01 Oct 07:35
Immutable release. Only release title and notes can be modified.
1f02776

Added

  • terraform-module-consumer: composes existing, versioned Terraform modules into Terraform or Terragrunt environment configurations, with state-safe validation and no direct managed resources or apply.
  • platform-builder: working rules for scope, change size, removed content, runtime dependencies and lockfiles; project values (registry, pull secret, repository path, partOf, component, subComponent) are suggested and confirmed with the user.
  • platform-builder: audit checks for the canonical PID 1 shape (ENTRYPOINT ["/usr/bin/dumb-init", "--"] with the process or a start script in CMD), chart command/args overrides and start scripts that do not exec.
  • platform-builder: chart checks for Service ports, named probe and route ports, empty pod securityContext, disabled mounts, hard-coded PVC claims, non-HTTP release overlays, per-mode subComponent, schema enums and minLength on empty defaults, unused optional blocks, undocumented job/cronjob/persistence leaves, and credentials in ConfigMaps, env values or args across all containers.
  • platform-builder: checks that the chart image equals the CI push path, placeholder registry and pull secret, AI/agent files present or committed (reported, never removed), changelog H1, SemVer for Project:Version:Init, and unknown extends: targets.
  • platform-builder: chart-lint.sh, chart-docs.sh, names.py and verify_siblings.py.
  • gitops-manager: argocd app add — service bootstrap steps and app_add.py, which adds a service's apps entry (single release or a release of a multi-release group) to an environment's root values.yaml, scaffolds its values/ file from the service chart with placeholders for environment values and credentials, never overwrites, and can render-check the new Application.
  • gitops-manager: override_check.py, which reports environment overrides that belong in the chart.

Changed

  • Every skill holds only its workflow instructions and scripts. Standards, contracts and starter templates are documented in the libraries the skills read at the resolved ref:
    • helm-tpl-library: chart description and README, the values replica, naming, container keys, derived names, routes, mounts and file mounts, rendering behaviour, secrets, schema, security posture, probes, renames, ignore files and charts with several releases;
    • gitlab-ci-library and github-ci-library: the include set and scenario files, project jobs, WORKFLOW options, job responsibilities, per-stack rules, Dockerfile standards (PID 1, base images, comments, # renovate:, cache handoff, .dockerignore, project base images) and the consumer security review;
    • argocd-gitops-tpl-library: the apps registry, what an environment values file overrides, the environment starter files and the GitOps README cluster convention;
    • terraform-modules: module consumption, provider-schema mapping, state migration, test shapes, other-provider tables and the architecture diagram template.
  • The skills name decision areas, never library file names: each reads a library's README index at the resolved ref and follows only the rows a task needs, so a library can rename, split or extend its guides without a skill release.
  • platform-builder: SKILL.md carries the update and audit steps (engine and judged findings) that the removed references held.
  • gitops-manager, terraform-module-builder and terraform-module-consumer name their library's public repository as the default source, at main, as platform-builder does in core/libraries.json; a source named in the request still wins. terraform-module-builder reads the current repository when it is terraform-modules and edits only a local checkout, and terraform-module-consumer reads the docs at the stack's pinned module source before any local checkout. The README lists where each skill resolves its libraries, and every gitops-manager prompt has a library source slot.
  • platform-builder: subComponent and chart names are suggestions, not a fixed vocabulary; subComponent is required only for multi-mode charts.
  • platform-builder: jobs, cronjobs, persistence, metrics and global.tracing are optional features, absent unless used; global.metrics may be omitted without a monitor entrypoint.
  • platform-builder: PID 1 findings are P1 against the canonical shape; comments in CI files are one line saying why.
  • platform-builder: README drift is detected by regenerating with helm-docs instead of file timestamps.

Removed

  • platform-builder: core/references/, platforms/*/references/ and assets/; gitops-manager: assets/bootstrap/; terraform-module-builder: references/ and assets/ — their content moved to the libraries above. The lists of known library defects are dropped; the one still open (Terraform:Check:README gating) is fixed in gitlab-ci-library.
  • platform-builder: the USE_DOCKER_BUILDX guidance and finding, merge-request instructions, the requirements-file and pyproject.toml indentation checks, and automatic removal of agent tooling.

Fixed

  • platform-builder: GitLab !reference tags parse; non-image ARG defaults and the project's own registry are no longer reported as external images; the Cross-Service Override Law check no longer fires on every sibling reference; a dependency-download job is required only when a language module is included; library pins are read from remote: include URLs.
  • platform-builder: suggested micro base image names match the published grootantech/micro-* repositories.

1.4.0

Required

  • Reinstall or re-link the skills from this release. platform-builder no longer ships
    core/references/, platforms/*/references/ or assets/, gitops-manager no longer ships
    assets/bootstrap/, and terraform-module-builder no longer ships references/ or
    assets/. Point anything that read those files, such as editor rules, project instructions
    or uploaded Project Knowledge, at the library documentation instead.
  • The standards now come only from the libraries, read at the resolved ref. A library pinned in
    .platform-builder.json or $PLATFORM_BUILDER_LIB_* must be at least the release listed in
    COMPATIBILITY.md; an older pin lacks the guidance the skills follow.
    The same applies to the terraform-modules checkout the Terraform skills read.

Recommended

  • Run platform update on onboarded repositories. The audit now reports a PID 1 shape other
    than ENTRYPOINT ["/usr/bin/dumb-init", "--"] with the process in CMD, chart
    command/args overrides and start scripts that do not exec as P1 findings.
  • argocd app add adds a service to an existing environment, and terraform-module-consumer
    composes infrastructure from released modules.

Verify

  • python3 platform-builder/core/scripts/libraries.py <repo> --all lists each library's
    README index and MIGRATION.md at the expected ref.

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.