Important Release Documents

Release Notes - Seatmap Platform

Version 1.58.2 - 2026-01-20

Release Focus: CI/CD Infrastructure - Release Numbering Fix

What’s New

Cleaner Version Numbers for Production Releases

We’ve fixed the version numbering system in our CI/CD pipeline to ensure production releases always have clean, semantic version numbers.

What This Means for You:

  • Clearer Version Identification: Production releases now use clean semantic versions like 1.59.0
  • Better Docker Tag Clarity: Docker images tagged with clear version numbers
  • Improved Release Tracking: Easier to identify and track production releases
  • Standards Compliance: Full semantic versioning compliance for production builds

Technical Details

Before This Fix: Production releases from the main branch could potentially include pre-release labels or build metadata, making version numbers less clear.

After This Fix:

  • Main branch builds: Clean semantic versions (e.g., 1.59.0)
  • Dev branch builds: Continue with commit identifiers for traceability (e.g., 1.59.1-beta.5-abc123d)
  • Tagged releases: Clean versions matching the tag

This change affects only the version numbering format in the CI/CD pipeline. All functionality remains identical.

Bug Fixes

CI/CD Pipeline

  • Fixed version number generation on main branch to produce clean semantic versions
  • Ensured GitVersion outputs MajorMinorPatch format for production releases
  • Improved consistency in Docker image tagging

What’s Inside

This release includes 1 commit focused on CI/CD infrastructure improvements:

Main Changes:

  1. GitVersion CI Configuration - Fixed version numbering logic for main branch builds

Components Updated:

  • CI/CD Pipeline - Version numbering logic

Migration Guide

For Existing Users

Excellent News: This release is 100% backwards compatible.

No code changes required
No configuration updates needed
No database migrations required
No API changes
Drop-in replacement for v1.58.0

This is purely an infrastructure improvement that affects how version numbers are generated during the CI/CD build process.

What Changed in Practice

Docker Image Tags:

  • Previous: Could include pre-release identifiers
  • Now: Clean semantic versions on production

GitLab Release Tags:

  • Previous: Potentially complex version strings
  • Now: Clean semantic versions like 1.59.0

Dev Builds:

  • Unchanged: Continue to include commit SHA for traceability
  • Example: 1.59.1-beta.5-abc123d

Testing Recommendations

No testing required for application functionality. To verify the fix:

  1. Check Pipeline Variables: Review GitLab CI/CD pipeline output for VERSION variable

    # Should show clean version on main branch
VERSION=1.59.0

  2. Verify Docker Tags: Check Docker registry for clean version tags

    docker pull registry/seatmap/booking-service:1.59.0

  3. Confirm GitLab Release: Release version should match semantic version format

Impact

Release Management

  • Clearer Versioning: Immediate identification of production release versions
  • Better Tracking: Simplified version comparison and history tracking
  • Reduced Confusion: Eliminated ambiguity in version identifiers

DevOps & Deployment

  • Cleaner Docker image tags
  • Simplified release artifact identification
  • Better compliance with semantic versioning standards
  • Easier rollback identification

Development Workflow

  • Dev branch versioning unchanged
  • Feature branch versioning unchanged
  • Only main branch production builds affected

Thank You

This release represents our commitment to clean infrastructure and clear release management. While the change is purely in the build pipeline, it improves clarity and traceability for production deployments.

What’s Next?

With clearer version numbering in place, we continue to work on:

  • Enhanced monitoring and observability
  • Improved deployment automation
  • Better release management tools
  • Additional CI/CD optimizations

Stay tuned for more updates!

Additional Documentation

For detailed technical information, see:

  • Deployment Guide - CI/CD pipeline changes and technical details
    • GitVersion configuration changes
    • Before/after version format examples
    • Impact on pipeline stages and Docker tags

Questions? Contact the Seatmap team or check our documentation at seatmap.pro.