Release notes

Devopsify ships on a weekly cadence. Every release is validated against the supported provider APIs, the OpenAPI contract, and the full test suite before it is tagged. This page tracks what changed, why, and which external API requirements drove each release.

Release cadence

Weekly, every Friday UTC

Supported provider APIs

AWS EC2, Azure Compute, GCP Compute — plus Hetzner, DigitalOcean, OVHcloud, Oracle, and on-prem agents

Active milestone

2026.33 — live SDK adapters in general availability

Timeline

Period	Focus
2024 Q4	Foundation: multi-tenant data model, auth/RBAC, tenant-scoped inventory
2025 H1	Control plane: provisioning plans, policy, approvals, audit, deployment waves
2025 H2	Connectivity: on-prem agents, CI/CD adapters, runbooks, guarded AI assistance
2026 H1	Real APIs: SDK-backed cloud adapters, credential validation, provider API version pinning
2026 H2	Operational depth: live cost allocation, drift evidence, wave coordination, FinOps forecasting

2026.33 — Live SDK adapters, general availability

Provider API requirements tracked

• AWS: EC2 DescribeInstances, DescribeVolumes, and DescribeTags now resolve through the pinned API version the SDK is built against. Accounts created before the December 2025 API retirement must re-validate their credentials.
• Azure: Compute and Resources clients were moved to the 2026-03-01 API version. Entra applications that predate the tenantId/clientId contract need their API permissions re-consented.
• GCP: Compute v1 instance discovery now requires the compute.instances.list and compute.disks.list scopes to be granted to the service account; the workload identity pool grant is re-checked at validation time.

This release

• Real SDK adapters for AWS, Azure, and GCP. When valid credentials are present, discovery, actions, and health checks run against the live provider API. Without credentials, evaluation falls back to the labeled demo inventory so the workspace never breaks.
• validateCredentials now performs a live provider call and reports a permission gap list instead of a format check.
• Credential redaction hardening: no secret material is stored, returned, or logged.
• Web: /pricing, /compare, and /faq public pages shipped with the pricing survey and access requests.

2026.32 — Weekly maintenance

• Worker: signed job envelopes for on-prem agent commands (poll, acknowledge, result).
• Docs: provider adapter guide updated with SDK-based enrollment steps.
• Security: tightened the public contact submission flow with server-side CAPTCHA verification.
• Fixed: command results were silently dropped when an agent posted to the legacy result path.

2026.31 — Access and evaluation

• Request Access flow: email, company, role, infrastructure type, scale, and purpose captured and routed to the platform team.
• Capacity note added to the public pricing surface; access is granted on a guided basis.
• Cookie consent: a real devopsify_consent cookie with a one-year lifetime now backs the consent banner.

2026.30 — Provider API compliance

• Pinned AWS, Azure, and GCP SDK versions after hyperscaler API deprecations announced in Q2 2026.
• Automated credential validation added to the cloud account enrollment wizard.
• Region and zone metadata refreshed for the providers tracked in the capability matrix.

2026.29 — Docs and SEO

• Docs clean-URL routing enabled; all /docs/* paths resolve without .html.
• Sitemap coverage extended to the full public surface and the documentation tree.
• Canonical host pinned to the www origin; GA measurement live on the site and the docs.

2026.28 — Guardrails

• Policy engine: pass / deny / review signals extended to provisioning plans and deployment waves.
• AI assistance: proposal review is now approval-gated in the worker path; the assistant never performs an unrestricted action.
• Runbook scheduler: typed runbook steps can be scheduled and traced to an actor and outcome.

2026.27 — On-prem agents

• Enrollment token lifecycle, heartbeat health, and agent capability detection.
• Command policy validation before an envelope is issued; everything outside the allowed command list is rejected.
• Agent key rotation and revocation surfacing in the tenant UI.

2025 H2 — Connectivity and automation

• Deployment sets: grouped changes move through waves with a shared review scope.
• CI/CD adapters: repository and pipeline signals normalized into the inventory.
• Runbooks: repeatable response steps with audit retention.
• AI DevOps Engineer: investigation assistance with scoped actions, approval guardrails, and a recorded decision trail.
• Digital twin: relationship and drift context assembled from normalized resources.

2025 H1 — The control plane

• Provisioning plans through OpenTofu with approval requirements and an immutable decision trail.
• Entitlements and policy evaluation before any change proceeds.
• Multi-cloud inventory with ownership, region, tags, and operational state.
• Change review: plans, policies, deployment waves, and audit records in one decision history.

2024 Q4 — Foundation

• Multi-tenant data model with organizationId scoping on every tenant-owned record.
• Auth, sessions, refresh tokens, RBAC, and organization membership.
• Tenant-scoped inventory and the public/authenticated boundary.
• The evidence-to-action loop that every release since has built on.

How releases are validated

• pnpm db:validate and pnpm openapi:validate run on every schema or contract change.
• The full unit, integration, and contract suites must pass before a tag is cut.
• Provider adapter changes are tested against the mock harness and, when credentials are available, a read-only live run.