Tags give the ability to mark specific points in history as being important
-
v2.0.0
protectedad783c74 · ·Release v2.0.0 - Production-Ready Enterprise Grade Major version bump with comprehensive documentation overhaul and tooling improvements. - ✅ Markdownlint integration (local + CI/CD) - ✅ 100% Markdown validation (30 files, 0 errors) - ✅ Documentation aligned with Dockerfile implementations - ✅ Badge system reorganized with semantic grouping - ✅ Node dev: ESLint, Prettier, Stylelint globally available - ✅ Node: All package managers documented (npm, npx, Yarn, pnpm) - ✅ PHP: UID/GID documentation corrected (1000) - ✅ Nginx: HTTP/3 false claim removed (HTTP/2 only) - ✅ Nginx: Vite config clarified as example - ✅ Redis: Sentinel scripts documented (check-sentinel.sh, test-failover.sh) - ShellCheck: 59 scripts, 100% compliance - Markdown: 30 files, 0 errors - Documentation coherence: 100% This tag triggers full build and promotion: 1. Validation (config, shellcheck, markdownlint) 2. Security (SAST, dependency scan, secrets, IaC) 3. Build (13 images: PHP, Node, MySQL, Redis, Nginx, services) 4. Test (health checks, sizes, multi-stage integrity) 5. Promote (registry push + Docker Hub sync) **Core Backend:** - php:8.3-prod, php:8.3-dev, php:8.3-test **Core Frontend:** - node:20-prod, node:20-dev, node:20-test **Databases:** - database:mysql-8.0, database:redis-7 **Web & Services:** - web:nginx-1.26 - services:mailhog, services:minio - services:e2e-testing, services:performance-testing 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
-
v1.5.0
protectedf15ed057 · ·Release v1.5.0 - Hybrid Script Validation Features: - Dual-layer script validation (critical + exhaustive) - 11 pipeline-essential scripts explicitly validated - 59 total scripts automatically discovered and checked - Clear separation between critical and optional scripts Improvements: - Maintenance-free: new scripts auto-detected - Better coverage reporting - Non-executable scripts flagged as recommendations Technical: - Option A (hardcoded critical) + Option C (automatic exhaustive) - Enhanced summary with detailed coverage info
-
v1.4.1
protected81e24041 · ·Release v1.4.1 - Fix Docker Hub sync non-blocking Bugfix: - Make Docker Hub description update non-blocking - Script no longer fails when API returns 403 - Images sync continues even if description update fails Technical: - Add || true pattern to update_dockerhub_description() call - Prevents set -euo pipefail from crashing script on API error
-
v1.4.0
protected48f77fae · ·Release v1.4.0 - Docker Hub Sync + Makefile Workflow Fix Features: - Automatic Docker Hub description sync via API v2 - 9 comprehensive README files for all images - Complete local build workflow (build-all, build-and-test) - Enhanced ShellCheck validation (59 scripts) - Complete documentation (DOCKER_HUB_SYNC.md, LOCAL_DEVELOPMENT.md) Standards: - ShellCheck 100% compliance - Enterprise-grade CI/CD pipeline - Production-ready documentation
-
v1.3.1
protectedf3e2410d · ·Release v1.3.1 - Documentation Consistency & Cleanup Documentation improvements: - Fix obsolete cleanup workflow documentation (commit e15e879 changes) - Remove scripts/cleanup.sh (obsolete since Dec 22, 2025) - Update CI/CD workflow docs (local-only staging, no registry pollution) - Correct image count (13 images everywhere) - Simplify Image Naming Conventions section - Add contextual badge placement (registries, images, platform) - Fix INDEX.md typo Infrastructure: - Remove cleanup stage from .gitlab-ci.yml (unused) - Update CLAUDE.md, README.md, REFERENCE.md for accuracy This release focuses on documentation accuracy and consistency. No functional changes to images or build process.
-
v1.2.6
protected351221ad · ·fix: use shared default builder for docker driver singleton Complete fix for OCI export timeouts on large images: - Use docker driver for local builds (avoid OCI export) [2d4f392] - Use shared default builder (docker driver singleton limitation) [351221a] - Remove --load flag for docker driver (automatic availability) [2d4f392] This resolves both the timeout issue and the builder creation conflict for MySQL, Redis, and all large service images in CI pipeline. Supersedes: v1.2.5 (incomplete - docker driver singleton issue) Fixes: v1.2.4 (OCI export timeout errors)
-
v1.2.5
protected2d4f392c · ·fix: resolve OCI export timeouts for large images (MySQL, Redis, services) - Use docker driver for local builds (PUSH_TO_REGISTRY=false) - Use docker-container driver for registry pushes (PUSH_TO_REGISTRY=true) - Remove --load flag for docker driver (automatic availability) - Fixes MySQL (134MB), Redis, and large service image build failures This resolves the 'unexpected EOF' errors during OCI export that affected large images when using docker-container driver with --load flag.
-
v1.2.3
protected8c461cf9 · ·Release v1.2.3 - Fix promote job dependencies Hotfix: Update promote:tags job dependencies to use new merged job names Fix: - Replace build:php:prod/dev/test with build:php - Replace build:node:prod/dev/test with build:node - Fixes 'undefined need' error in promote stage This completes the pipeline refactoring from v1.2.2.
-
v1.2.2
protected9ff0f23c · ·Release v1.2.2 - Pipeline optimization and local testing Major Improvements: - Merge 6 build jobs into 2 (build:php, build:node) - Each job builds all stages (prod/dev/test) sequentially - Remove 2 pipeline stages (build-dev, build-test) - Fix test scripts to use local images instead of registry pulls Performance: - Faster builds: 6 jobs → 2 jobs - Better cache efficiency (shared BuildKit layers) - Simpler pipeline: 8 stages → 6 stages - Reduced execution time Fixes: - test:image-sizes now checks local images - test:multi-stage-integrity uses docker inspect - All tests work without registry access Pipeline flow now: validate → security → build-prod → services → test → promote
-
v1.2.1
protected42aa3c08 · ·Release v1.2.1 - Fix local build strategy Critical Fix: - Build script now respects PUSH_TO_REGISTRY from CI/CD environment - Images are correctly built locally without pushing to registry The v1.2.0 release had a bug where the build script was overriding the PUSH_TO_REGISTRY variable, causing staging images to still be pushed to the registry. This patch fixes the issue - staging images will now stay on the runner and only stable tags will be pushed to GitLab Container Registry.
-
v1.2.0
protectede15e879f · ·Release v1.2.0 - Local Build Strategy Major Change: Build images locally on runner instead of pushing staging tags Features: - Build images locally on runner (no registry pollution) - Promote only stable tags to GitLab Container Registry - Add latest-test variants to Docker Hub sync - Disable cleanup job (handled by runner's daily cleanup) Benefits: - 100% cleaner registry (no staging tags visible) - Faster builds (no push/pull overhead) - Reduced registry storage usage - Simplified CI/CD workflow Breaking Changes: - Requires all jobs to run on same runner - Requires runner with shared Docker daemon - Staging images no longer available in registry This is a MINOR version bump (1.1.x → 1.2.0) due to workflow changes.