Skip to content

RELEASES.md

Latest commit

 

History

History
112 lines (78 loc) · 4.53 KB

RELEASES.md

File metadata and controls

112 lines (78 loc) · 4.53 KB
Raw

KServe Release Policy

This document describes the release policy for the KServe project, including release cadence, versioning, support windows, and what users can expect from each release.

For the detailed release process used by release managers, see release/RELEASE_PROCESS.md.

Release Cadence

KServe targets a new minor release every 8 weeks. The actual timing may vary based on feature readiness, critical bug fixes, or community needs.

Each release cycle follows this timeline:

Week Milestone
1-5 Development
5 Feature freeze, RC0
6 RC1+ (if needed)
7-8 Final GA release

Versioning Scheme

KServe follows Semantic Versioning with the format 0.MINOR.PATCH:

  • Minor release (0.Y.0): Contains new features, improvements, and bug fixes.
  • Patch release (0.Y.Z): Contains only security fixes for supported versions. No bug fix backports except breaking change; users should upgrade to the latest minor release.
  • Release candidate (0.Y.0-rcN): Pre-release for testing before a GA release.

Note: KServe is pre-1.0 and follows a 0.Y.Z scheme. Minor version bumps (Y) may include breaking changes. Breaking changes are documented in release notes.

Release Types

Type Tag Format Purpose
Release Candidate v0.Y.0-rcN Pre-release for community testing. Not for production use.
GA (Stable) v0.Y.0 Production-ready release with full support.
Patch v0.Y.Z Security fixes only(breaking change) for supported versions.

Support Policy

KServe maintains support for the latest two minor releases:

  • Latest minor release (N): Receives security patches as patch releases.
  • Previous minor release (N-1): Receives critical security patches only.
  • Older releases (N-2 and below): Not supported. Users should upgrade.

Bug fixes are not backported to older releases. With an 8-week release cadence, users are encouraged to upgrade to the latest minor release to receive all fixes.

Supported Versions

Version Release Date Status
v0.19 Jun 12, 2026 Active - latest
v0.18 Apr 29, 2026 Security patches only
v0.17 Mar 13, 2026 End of life

Kubernetes Compatibility

Each KServe release is tested against specific Kubernetes versions. Refer to the compatibility matrix in the documentation for details.

Deprecation Policy

  • Deprecated features are announced at least one release cycle before removal.
  • Deprecations are listed in the release notes of the version where they are deprecated.
  • Deprecated APIs continue to function for at least one additional release after the deprecation announcement.

Release Artifacts

Each release includes the following artifacts:

Artifact Location
Container images GitHub Container Registry
Python packages PyPI (kserve), PyPI (kserve-storage)
Helm charts GHCR Helm Registry
Install manifests Included in each GitHub Release
Release notes Auto-generated on each GitHub Release

Release Management

Releases are performed by release managers, selected from the project's OWNERS file (approvers and above). A release manager is designated for each release cycle and is responsible for:

  • Coordinating the release timeline and feature freeze
  • Running the release process (release/RELEASE_PROCESS.md)
  • Publishing release candidates and the final release
  • Communicating release status to the community

For project governance and roles, see the KServe Community repository.

Release Announcements

Releases are announced through:

Security

For reporting security vulnerabilities and the security patch process, see SECURITY.md.