Overview
The Changelog provides a structured, chronological record of all notable changes to the StrataGateway platform. It serves as the authoritative source for users to understand what has changed between releases, including new features, improvements, bug fixes, deprecations, and breaking changes.
The StrataGateway changelog is currently being designed alongside the platform. No production changelog exists yet. All examples and structures below are illustrative of the planned format.
Current State
The public StrataGateway changelog does not yet exist. This page describes the planned structure and conventions that will govern the changelog once the platform reaches public availability.
Development Preview
The changelog format, categories, and conventions described here are still under design and may evolve before the first public release.
What Belongs in the Changelog
The changelog captures changes that affect external consumers of the StrataGateway platform:
Internal refactorings, code reorganizations, test additions, and other changes with no externally observable effect are not included in the public changelog.
Change Categories
Every changelog entry uses one of the following standard categories:
Entry Structure
Each changelog entry follows a consistent structure:
Release Identifiers
Releases are identified using a versioning scheme that allows users to understand the scope of changes:
The final versioning scheme will be confirmed before the first public release.
Dates and Timestamps
All changelog entries include an ISO 8601 date. Release entries include a release date; individual change entries may include the date the change was merged or released.
Date format
2026-07-29Dates use the ISO 8601 format (YYYY-MM-DD) for unambiguous parsing and sorting.
Breaking Changes
Breaking changes are called out explicitly in a dedicated section within each release. They include migration guidance and, where applicable, a deprecation timeline.
Breaking Changes section
### Breaking Changes
**API Authentication**
- `Authorization` header format changed from `Token <token>` to `Bearer <token>`.
- Legacy token format will be rejected after 2026-12-31.
**Instance Lifecycle**
- `DELETE /v1/instances/{id}` no longer supports `force=true` parameter.
- Use `POST /v1/instances/{id}/actions/terminate` instead.Breaking changes must include a migration path and, where applicable, a deprecation timeline with a concrete removal date.
Deprecations
Deprecated features are clearly marked with a removal timeline and a recommended migration path.
Deprecations section
### Deprecations
**Legacy CLI Command**
- `strata instance list` is deprecated.
- Use `strata compute list` instead.
- Removal planned for 2027-01-01.Security-Related Changes
Security-related changes are documented with appropriate detail while following responsible disclosure practices.
Security section
### Security
**TLS Configuration**
- Minimum TLS version raised to 1.2 for all API endpoints.
- TLS 1.0 and 1.1 connections will be rejected.
**Certificate Rotation**
- Platform TLS certificates rotated on 2026-07-15.
- No action required for SDK users.Security fixes follow responsible disclosure. Details of vulnerabilities are published only after a fix is available and users have had time to upgrade.
API Changes
Changes to the REST API surface are documented with sufficient detail for consumers to update their integrations.
Infrastructure Changes
Changes to the underlying platform infrastructure that may affect customer workloads:
Developer Tooling Changes
Updates to the developer experience ecosystem:
Release History
Planned releases with illustrative dates and themes:
Dates and themes are illustrative. Actual release cadence and content will be determined as the platform matures.
Notifications
Planned channels for changelog update delivery:
Inspect existing project plans before presenting any channel as committed.
Roadmap Relationship
The changelog documents what has been released. The Roadmap documents what is planned. They are complementary but distinct:
Changelog
Past-tense record of shipped changes. Immutable once published.
Roadmap
Forward-looking plan. Subject to change based on priorities and feedback.
Was this page helpful?