• Documentation
  • Tutorials
  • Blogs
  • Product

What's on this Page

    • Overview
    • Step Platform
    • Release Process
    • Roadmap
    • Compatibility
    • Related Resources
    • Support Channels
  • Step
  • Release Strategy
  • Release Cycle
Categories: RELEASE
This article references one of our previous releases, click here to go to our latest version instead.

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

Automation Package

  • Versioning follows the Step platform release cycle
  • Single version across all programming language implementations (Java, .NET, Node.js)
  • Released with each Step version

See: Automation Package Overview

Keyword API

  • Independent versioning allows updates without Step platform changes
  • Major versions introduce new capabilities

See: Keyword API Release Strategy

Docker Images

  • Released with each Step version
  • Updated for security patches and base image updates
  • Follow Step platform versioning

See: Docker Image Release Strategy

Release Process

Communication

Release information is communicated through:

  • Release Notes
  • News Section
  • GitHub Releases
  • Email Notifications: Subscribe to Step updates at step.dev

Roadmap

Step maintains a public roadmap outlining planned features and improvements:

  • Roadmap

Compatibility

Backward Compatibility

Step maintains backward compatibility where possible:

  • Keyword API: Older API versions typically work with newer Step versions
  • Automation Packages: Older schema versions can be deployed on newer Step instances by explicitly setting the schema version in the YAML descriptor
  • Plans: Plans manually created in Step are automatically upgraded when the Step version is
  • Data: Database migrations handled automatically where possible

Forward Compatibility

Forward compatibility is not guaranteed:

  • Plans or configurations from newer versions may not work on older versions
  • Always backup before upgrading

Related Resources

  • Step Platform Release Strategy
  • Helm Chart Release Strategy
  • Automation Package Overview
  • Keyword API Release Strategy
  • Docker Image Release Strategy
  • Agent Runtime Release Strategy
  • Roadmap

Support Channels

For questions about releases or support:

  • GitHub Repository
  • Documentation

See Also

  • Agent Runtime Docker Image Release Strategy
  • Step Docker Image Release Strategy
  • Step Helm Chart Release Strategy
  • Step Keyword API Release Strategy
  • Step Platform Release Strategy
  • Home
  • Whats new?
  • Release Strategy
    • Step Platform
    • Step Keyword API
    • Step Chart
    • Step Docker image
    • Agent runtime Docker image
    • Release Cycle
  • Set up
  • Administration
  • SaaS guide
  • User guide
  • Developer guide
  • DevOps
  • Plugins
  • Libraries
Step Logo
    • Documentation
    • Tutorials
    • Blogs
    • Product
    • Home
    • Whats new?
    • Release Strategy
      • Step Platform
      • Step Keyword API
      • Step Chart
      • Step Docker image
      • Agent runtime Docker image
      • Release Cycle
    • Set up
    • Administration
    • SaaS guide
    • User guide
    • Developer guide
    • DevOps
    • Plugins
    • Libraries