Skip to Content
Migration guides:Kubling 26.5 namespace, JDBC and error-code changes →KDV 26.3+ CLI project and test workflow changes →
ConceptsVersioning

Versioning

Kubling Core uses a three-segment release format:

YEAR.RELEASE[.FIX]
  • Year identifies the release year
  • Release increments for each feature release in that year
  • Fix is optional and increments for compatible fixes to that release

Examples:

  • 25.1 is the first feature release of 2025
  • 25.1.2 is the second fix for that feature release

Fix releases normally preserve the feature set, but may include small user-visible corrections required to make existing behavior work as documented.

Component versions

A version identifies one published component, not the entire Kubling platform. Kubling Core and KDV use independent release streams. Providers, client libraries and other independently distributed components own their respective versions as well.

In a KDV project:

  • the generated ./kdv launcher pins the CLI image
  • runtime.image selects the Kubling image used by the project environment
  • compose.yaml selects provider and supporting-service images
  • the production deployment selects its project-specific or official Kubling image and any external runtime artifacts
  • application dependencies select their client library versions

Record and upgrade these versions independently. Use the release notes and compatibility guidance of each component instead of assuming that equal version numbers are required.

Last updated on
DBeaverEnvironment Variables