1. Release Notes
  2. Release 1.58.2

Deployment & Settings Changes - v1.58.2

Release: v1.58.2
Date: 2026-01-20

Summary

Impact Level: LOW

Action Required: NO

Backward Compatible: YES

Quick Decision Matrix

This table provides a comprehensive at-a-glance view of all deployment changes, risks, and required actions for quick decision-making.

Component/Area Change Type Risk Level Action Required Impact
Environment Variables No changes NONE NO No environment variables affected
Database Schema No changes NONE NO No database changes
Database Modules No changes NONE NO No module structure changes
JooQ Configuration No changes NONE NO No JooQ changes
Docker Images No changes NONE NO Only version tags affected (format change)
Kubernetes/Helm No changes NONE NO No K8s configuration changes
Runtime Dependencies No changes NONE NO No dependency updates
Build Dependencies No changes NONE NO No build tool updates
Monitoring/Logging No changes NONE NO No monitoring changes
CI/CD Pipeline Modified LOW NO Version numbering logic updated

Deployment Decision

Overall Risk: LOW

Recommended Action: APPROVE

Downtime Required: NO - Zero-downtime supported

Rollback Risk: SAFE - Simple git revert

Special Considerations: NONE

Configuration Changes

Environment Variables

No New Variables

No environment variable changes in this release

No Modified Variables

All existing environment variables remain unchanged.

No Deprecated Variables

No deprecations in this release.

Database Changes

Migrations

New Migrations: NO

Note: This release contains no database changes. It only modifies the CI/CD pipeline logic for version number generation.

CI/CD Pipeline Changes

GitVersion Configuration Update

What Changed: Modified version number generation logic for main branch builds

Location: .gitlab/ci/gitversion-ci.yml

Modification:

# Added to version generation logic
elif [ "${CI_COMMIT_REF_NAME}" == "main" ]; then
  VERSION=$(grep 'GitVersion_MajorMinorPatch=' gitversion.properties | sed -e 's/GitVersion_MajorMinorPatch=//g')
fi

Purpose: Ensure main branch builds use clean semantic version numbers (e.g., 1.59.0) instead of versions with pre-release labels or build metadata.

Version Format Changes

Before This Release

Main Branch:

  • GitVersion could output: 1.58.0-1+2 or 1.58.0 (inconsistent)
  • Depended on GitVersion configuration mode
  • Could include pre-release identifiers

Dev Branch:

  • Outputs: 1.58.2-beta.5-abc123d (with commit SHA)
  • Behavior unchanged

Tagged Releases:

  • Used tag version: 1.58.0
  • Behavior unchanged

After This Release

Main Branch:

  • Always outputs clean semantic version: 1.59.0
  • Explicitly extracts MajorMinorPatch component
  • Consistent production-ready format

Dev Branch:

  • Still outputs: 1.59.1-beta.5-abc123d (with commit SHA)
  • No change in behavior

Tagged Releases:

  • Still uses tag version: 1.59.0
  • No change in behavior

Impact on Pipeline Stages

Affected Stages:

  • .pre stage (GitVersion calculation) - Logic updated
  • docker stage - Uses VERSION variable (format now cleaner on main)
  • release stage - Uses VERSION variable (format now cleaner on main)

Unaffected Stages:

  • build stage - No changes
  • sonar stage - No changes
  • deploy stage - No changes (uses same VERSION variable)

Pipeline Variables:

  • VERSION - Format changes on main branch only
  • GitVersion_MajorMinorPatch - Explicitly used for main branch
  • All other variables unchanged

Docker Image Tagging

Before:

  • Main branch tags: Could vary based on GitVersion output
  • Example: booking-service:1.58.0-1 (potential suffix)

After:

  • Main branch tags: Always clean semantic version
  • Example: booking-service:1.59.0

Tag Strategy (Unchanged):

  • 1.58.2 - Every commit (format improved on main)
  • latest - Only on main branch
  • 1.58.x:1.58.2 - For git tags

Registry Impact:

  • Existing images unchanged
  • New images from main will have cleaner tags
  • No breaking changes to tag format structure

Docker & Container Changes

No Docker Changes

No changes to Docker images, Dockerfiles, or container configurations in this release.

Only the version tag format is affected on main branch builds.

Kubernetes / Helm Changes

No Helm Changes

No changes to Helm charts or Kubernetes deployments in this release.

The deployment process remains identical; only the VERSION variable format changes on main branch.

Dependencies

Runtime Dependencies

No Updated Dependencies

All runtime dependencies remain at their current versions.

No New Dependencies

No new dependencies added in this release.

Build Dependencies

No changes to Gradle, Node.js, or other build tool versions.

CI/CD Deployment

Automated Deployment via GitLab CI/CD

This release is deployed automatically through GitLab CI/CD pipelines. No manual deployment steps are required.

Deployment Flow:

  1. Merge to dev: Auto-deploys to dev.seatmap.dev environment
  2. Merge to main: Manual trigger to deploy to seatmap.pro production

Pipeline Stages:

  • .pre stage - Version calculation (updated logic)
  • build stage - Compiles all components (unchanged)
  • sonar stage - Code quality analysis (unchanged)
  • docker stage - Builds Docker images with cleaner version tags
  • deploy stage - Kubernetes deployment (unchanged)
  • release stage - Creates GitLab releases with clean versions

Zero-Downtime: Fully supported

Action Required: NONE - Pipeline logic change is transparent to deployment process

Rollback

Rollback Support: Automated via GitLab CI/CD

Database Rollback: Not applicable (no database changes)

Procedure: Simple git revert of the commit modifying .gitlab/ci/gitversion-ci.yml

# If rollback is needed
git revert <commit-hash>
git push origin main

# Pipeline will automatically use previous versioning logic

Rollback Risk: SAFE - No data changes, no API changes, purely pipeline logic

Monitoring & Health Checks

New Metrics

No new metrics in this release

Health Checks

No changes to health check endpoints

Log Changes

No changes to application logging. Pipeline logs will show cleaner VERSION values on main branch builds.

Example pipeline log output:

VERSION=1.59.0
KUBE_ENV=prod

Known Issues

None - No known deployment issues

Release Notes Summary

What Changed

  1. CI/CD Version Numbering: GitVersion logic updated for main branch

    • Extracts clean MajorMinorPatch component
    • Ensures semantic version compliance
    • Improves Docker tag clarity

  2. Pipeline Variables: VERSION format improved on main branch

    • Cleaner version strings
    • Better release identification
    • Consistent production formatting

What Didn’t Change

  • Application code - No changes
  • Database schema - No changes
  • API endpoints - No changes
  • Configuration files - No changes (except CI/CD pipeline)
  • Environment variables - No changes
  • Dependencies - No changes
  • Deployment process - No changes (same steps)
  • Dev branch versioning - No changes (still includes commit SHA)

Support

Questions

Escalation

Standard escalation procedures apply - no special considerations for this release.

Sign-Off

Deployment Risk: LOW

Rollback Safety: SAFE

Downtime Required: NO

Special Steps: NONE

This release is a low-risk deployment with no impact on application functionality. It improves version number clarity in the CI/CD pipeline for production releases from the main branch.