Summary

Full release preparation and validation for Sztab 1.9.3 including:

• Version alignment across multi-module Maven project
• Backend image build and push (linux/amd64 via buildx)
• Staging deployment refresh via Helm
• Regression testing of core workflows
• Release notes and README_FIRST preparation
• Documentation restructuring (sztabctl extraction)
• Removal of tracked binary artifact
• Image pull troubleshooting and resolution

Scope of Work

1. Version Alignment

• Updated root pom.xml to 1.9.3

• Corrected module POM versions (backend, query-dsl, query-cli)

• Resolved parent POM mismatch causing Maven build failure

• Verified reactor build consistency via:

  mvn clean package -DskipTests

2. Docker Image Build & Push

• Built backend image using buildx:

  docker buildx build
  --platform linux/amd64
  -f backend/docker/Dockerfile
  -t tigase.dev/sztab/sztab-backend:1.9.3
  --push
  .

• Verified manifest list export

• Confirmed successful push to tigase.dev registry

• Resolved staging ImagePullBackOff caused by missing image

3. Helm Staging Deployment

• Restarted staging backend deployment:

  kubectl rollout restart deployment sztab-backend -n sztab-staging

• Verified rolling update behavior

• Confirmed pod ready state

• Verified correct image tag in running container

4. Regression Testing

Performed manual regression testing on:

• User profile modification
• Password change
• User creation (internal, partner, customer)
• Issue creation
• Issue filtering (GUI)
• Issue filtering (DSL)
• PR creation
• Regular merge
• Rebase merge
• Fast-forward merge
• Squash merge
• Merge retry after failure (SZ-111 validation)
• PAT refresh behavior (SZ-110 validation)

All flows verified functional in release image.

5. Release Documentation

• Renamed docs/release/1.9.2 → 1.9.3
• Updated ReleaseNotes.md
• Updated README_FIRST.md
• Validated all links
• Verified image tags referenced in documentation
• Extracted sztabctl documentation to docs/tools/sztabctl.md
• Ensured historical release notes preserved

6. Cleanup

• Removed tracked binary artifact (sztabina executable)

• Verified git status clean before tagging

• Tagged release:

  v1.9.3

• Confirmed tag alignment with HEAD

Lessons Learned

• All module POM versions must be aligned before image build
• Backend image must be pushed before release announcement
• Multi-module Maven versioning should use versions:set
• Build verification should precede release email

Outcome

Staging successfully upgraded to 1.9.3. Release artifacts aligned. Regression suite manually validated.

Release declared stable.