Tags & Releases

The project follows the Semantic Versioning format for all tags and releases:

X.Y.Z  →  Major.Minor.Patch

Each part is incremented as follows:

  • Major – Breaking changes or significant new features

  • Minor – Backward-compatible new functionality

  • Patch – Bug fixes and small improvements


Note

Tags are automatically created via the CI/CD pipeline. During the pipeline run, you can select which version component to increment — Major, Minor, or Patch — and the pipeline will automatically bump the version number and publish the new tag and release.


Registering a New Version

Before tagging a release, update the active version in the data.json fixture file located at rdmc/fixtures/data.json.

  1. Set the current active version to "is_active": false.

  2. Add a new entry with the new version_number, release_date, and "is_active": true.

  3. Only one version should have "is_active": true at any time.

  4. Proceed with creating the Git tag — the tag name should match version_number exactly (e.g., 0.7.0).

The fixture entry format is as follows:

{
  "model": "rdmc.projectversion",
  "fields": {
    "version_number": "0.7.0",
    "release_date": "2026-06-01",
    "is_active": true
  }
}

Note

The active ProjectVersion controls the documentation URL and the version displayed in the platform UI. Mismatches between the Git tag and the database entry will cause broken documentation links.


Available Tags & Releases

—
Total Tags
—
Total Releases

Loading...