Release v1.0.3

Multi-engine support

v1.0.2

Full Changelog: v1.0.1...v1.0.2

v1.0.1

🚀 PostgreSQL 18 Upgrade

This release upgrades the PostgreSQL service to PostgreSQL 18, aligning the Docker Database Stack with upstream architectural changes and improving long-term upgrade safety.

---

🔄 What’s Changed

• Upgraded PostgreSQL from 17 → 18
• Updated PostgreSQL data directory layout to follow PostgreSQL 18+ standards
• Base volume mount moved to /var/lib/postgresql
• Data is now stored in major-version-specific subdirectories
• Volume layout is compatible with:
  • pg_ctlcluster
  • pg_upgrade --link
  • Future major PostgreSQL upgrades

---

⚠️ Breaking Change

PostgreSQL 18+ is not backward-compatible with data volumes created by PostgreSQL 17 or earlier.

• Reusing old volumes will fail on startup by design
• This behavior prevents silent data corruption during major version upgrades

Required Actions

• Development / fresh environments
  • Remove existing PostgreSQL volumes and reinitialize the database
• Production environments
  • Perform a proper pg_upgrade using PostgreSQL 17 and 18 binaries

---

🛠 Operational Notes

• Existing tooling (setup.sh, reset-databases.sh) fully supports PostgreSQL 18
• Ownership and permission model remains unchanged:
  • Data directories owned by postgres (UID 999)
  • Strict permissions (700) enforced

---

🏷 Versioning

• Tagged as v1.0.1
• Classified as a PATCH release with intentional, documented breaking behavior
• Future PostgreSQL major upgrades will continue to follow explicit upgrade paths

Initial Stable Release

🎉 Initial Stable Release

This is the first production-ready release of the Docker Database Stack.

Highlights:

• MySQL 8.4 (LTS) & MariaDB 11.4 (LTS)
• PostgreSQL 17 with strict data permissions
• PgBouncer with SCRAM-SHA-256 authentication
• Centralized .env configuration
• setup.sh & reset-databases.sh workflow

See CHANGELOG.md for full details.