https://step.dev/knowledgebase/30/releasestrategy/ Recent content in Release Strategy on Step Documentation Hugo -- gohugo.io en Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/step-release/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/step-release/ Overview The Step platform follows a structured versioning and release strategy to ensure stability and predictable updates for users. This page describes the versioning scheme, release cadence, and upgrade path for the core Step platform. Versioning Scheme Step uses a distinctive versioning format: Major.Minor (e.g., 27.4, 28.3, 29.0) Major version: The first number (e.g., 27, 28, 29) - Incremented for significant releases containing new features and major enhancements Minor version: The second number (e. https://step.dev/knowledgebase/30/releasestrategy/keyword-api-release/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/keyword-api-release/ Overview The Step Keyword API is maintained and versioned independently of the Step platform. This independent versioning allows for more flexible updates and backward compatibility across different Step versions. Versioning Scheme The Keyword API follows semantic versioning with the format: MAJOR.MINOR.PATCH Major version: Significant API changes or breaking changes Minor version: New features and enhancements Patch version: Bug fixes and minor improvements Independent Versioning The Keyword API uses a single version across all supported programming languages (Java, . https://step.dev/knowledgebase/30/releasestrategy/chart-release/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/chart-release/ Overview The Step Helm Chart is versioned independently from the Step platform itself. This separation allows for chart-specific improvements, Kubernetes compatibility updates, and configuration enhancements without requiring Step platform upgrades. Versioning Scheme The Helm Chart follows semantic versioning with the format: MAJOR.MINOR.PATCH Major version: Breaking changes or significant architectural changes Minor version: New features and enhancements Patch version: Bug fixes and minor improvements Chart Compatibility Matrix The Helm Chart version must be compatible with your Step version. https://step.dev/knowledgebase/30/releasestrategy/docker-image-release/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/docker-image-release/ Overview Step provides official Docker images for Step components, enabling containerized deployments in Docker, Kubernetes, and other container orchestration platforms. These images are versioned to match the Step platform version they contain. Image Repositories Official Step Docker images are available from the Exense Docker registry at docker.exense.ch/step-enterprise. These images include: Step Controller: The main Step controller application Step Agent: The Step agent for executing keywords Step Grid Proxy: The grid proxy component For agent runtime images, see Agent Runtime Docker Images which provide the execution environment for the Step Agents. https://step.dev/knowledgebase/30/releasestrategy/agent-runtime-release/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/agent-runtime-release/ Overview Step Agent runtime Docker images provide the execution environment for running Agents. These images are separate from the Step Controller and Agent images and are released independently of Step platform releases. Official Agent Runtime Images Step provides two types of official agent runtime images from docker.exense.ch/step-enterprise: Important: A new naming convention for agent runtime images is being introduced. For details on the changes, timeline, and migration instructions, see the Agent Runtime Image Naming Convention Migration Guide. https://step.dev/knowledgebase/30/releasestrategy/release-cycle/ Tue, 14 Oct 2025 00:00:00 +0000 https://step.dev/knowledgebase/30/releasestrategy/release-cycle/ Overview This page provides an overview of the release cycles and cadences for Step and its ecosystem components. Each component follows its own independent release strategy to provide flexibility and stability. Step Platform For detailed information about Step’s versioning scheme, release cadence, and support policy: Step Platform Release Strategy Component-Specific Release Cycles Different Step components follow independent release cycles: Helm Chart Released as needed for Kubernetes compatibility and configuration improvements Major versions typically aligned with significant Step releases See: Helm Chart Release Strategy