1. Release Notes
  2. Release 1.58.0

Deployment & Settings Changes - v1.58.0

Release: v1.58.0
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 configuration updates needed
Database Schema No changes NONE NO No migrations to run
Database Modules Reorganization LOW NO Build-time only, automatic
JooQ Configuration Enhancement LOW NO Opt-in feature, backward compatible
Docker Images No changes NONE NO No container updates
Kubernetes/Helm No changes NONE NO No deployment config changes
Runtime Dependencies No changes NONE NO No library updates
Build Dependencies New module LOW NO Handled by build system
Monitoring/Logging Enhanced LOW NO Automatic improvement

Deployment Decision

Overall Risk: LOW

Recommended Action: APPROVE

Downtime Required: NO

Rollback Risk: SAFE (no database changes)

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: While database migrations have been reorganized into a separate module, no new database schema changes are included in this release.

Module Reorganization

Database migrations have been moved from editor-service to a dedicated db-migrations module for better organization:

Old Structure:

editor-service/
└── src/main/resources/db/migration/
    ├── V87__*.sql
    ├── V88__*.sql
    └── ...

New Structure:

db-migrations/
├── build.gradle
└── src/main/resources/db/migration/
    ├── V87__*.sql
    ├── V88__*.sql
    └── ...

Impact:

  • Yes - No database changes
  • Yes - No migrations to run
  • Yes - Existing migrations are unchanged
  • Yes - Migration history preserved
  • Yes - No deployment impact

Benefits:

  • Clearer separation of concerns
  • Easier to track migration history
  • Independent versioning possible
  • Better support for multiple environments
  • Simplified rollback procedures

JooQ Configuration Changes

Extended Configuration

What Changed: JooQ configuration now supports configurable schema names

Location: booking-service/jooq.gradle

New Options:

jooq {
  // New: Configurable schema name
  configurations {
    main {
      generationTool {
        database {
          name = project.findProperty('jooq.schema') ?: 'public'
        }
      }
    }
  }
}

Benefits:

  • Support for multi-tenant deployments
  • Can target different schemas in different environments
  • Better code generation flexibility
  • Improved type safety

Action Required: NO

  • Default behavior unchanged
  • Existing configurations continue to work
  • New option is opt-in

Docker & Container Changes

No Docker Changes

No changes to Docker images or configurations in this release.

Kubernetes / Helm Changes

No Helm Changes

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

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

Gradle Module Structure

What Changed: Added new db-migrations module to Gradle build

Impact: Build-time only, no runtime impact

settings.gradle:

include 'db-migrations'  // New module added
include 'editor-service'
include 'booking-service'
include 'common-lib'

Action Required: NO

  • Handled automatically by build system
  • No developer action needed

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 seatmap.dev environment
  2. Merge to main: Manual trigger to deploy to seatmap.pro production

Pipeline Stages:

  • Yes - Build (Gradle handles new db-migrations module automatically)
  • Yes - Test
  • Yes - Docker image creation
  • Yes - Kubernetes deployment
  • Yes - Health checks

Zero-Downtime: Fully supported via Kubernetes rolling updates

Action Required: NONE - Pipeline handles everything automatically

Rollback

Rollback Support: Automated via GitLab CI/CD

Database Rollback: Not applicable (no schema changes in this release)

Procedure: Revert commit or redeploy previous version through GitLab pipeline

Monitoring & Health Checks

New Metrics

No new metrics in this release

Health Checks

No changes to health check endpoints

Log Changes

Enhanced Logging:

  • Version information now included in Sentry error reports
  • Helps identify version-specific issues faster

Example log entry:

{
  "version": "1.58.0",
  "component": "booking-renderer",
  "error": "...",
  "timestamp": "2026-01-20T12:00:00Z"
}

Action Required: NO

  • Automatic improvement
  • No configuration changes needed

Warning - Known Issues

None - No known deployment issues

Release Notes Summary

What Changed

  1. Database Migrations Module: Organizational change only

    • Migrations moved to dedicated module
    • No schema changes
    • No deployment impact

  2. JooQ Configuration: Enhanced with configurable schema names

    • Opt-in feature
    • No action required
    • Backwards compatible

  3. Version Logging: Added to error reports

    • Automatic improvement
    • Better debugging capability

What Didn’t Change

  • Yes - No database schema changes
  • Yes - No environment variables
  • Yes - No Docker images
  • Yes - No Kubernetes configuration
  • Yes - No runtime dependencies
  • Yes - No breaking changes

Support

Questions

Escalation

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

Yes - Sign-Off

Deployment Risk: LOW

Rollback Safety: SAFE (no database changes)

Downtime Required: NO

Special Steps: NONE

This release is a low-risk deployment with no infrastructure changes, database migrations, or configuration updates required.