Skip to content

Update uselagoon/mysql-8.4 Docker tag to v26.2.0 #145

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
AlexSkrypnyk merged 1 commit into from
Feb 24, 2026
Merged

Update uselagoon/mysql-8.4 Docker tag to v26.2.0 #145

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docker-compose.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,7 +157,7 @@ services:
context: .
dockerfile: .docker/database.dockerfile
args:
IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.1.0}" # Use custom database image (if defined) or fallback to standard database image.
IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}" # Use custom database image (if defined) or fallback to standard database image.
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot Feb 23, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix YAML inline comment spacing to satisfy lint.

Line 160 has only one space before the inline comment; YAMLlint expects two.

🔧 Proposed fix 
-        IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}" # Use custom database image (if defined) or fallback to standard database image.
+        IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}"  # Use custom database image (if defined) or fallback to standard database image.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}" # Use custom database image (if defined) or fallback to standard database image.
IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}" # Use custom database image (if defined) or fallback to standard database image.
🧰 Tools
🪛 YAMLlint (1.38.0)

[warning] 160-160: too few spaces before comment: expected 2

(comments)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` at line 160, The inline comment on the IMAGE definition
(the IMAGE: "${VORTEX_DB_IMAGE:-uselagoon/mysql-8.4:26.2.0}" line) has only one
space before the comment; update that line to use two spaces before the inline
comment to satisfy YAML linting rules (i.e., ensure there are two spaces between
the value and the "#" comment marker while keeping the same value and comment
text).

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

uselagoon/mysql-8.4:26.2.0 Docker image tag lagoon-images release

💡 Result:

uselagoon/mysql-8.4:26.2.0 is the MySQL 8.4 Lagoon image built and published as part of the uselagoon/lagoon-images release 26.2.0 (released Feb 23, 2026). In that release, the MySQL base was updated to upstream mysql:8.4.8 (Oracle Linux variant), so this tag contains MySQL 8.4.8 plus Lagoon’s standard adaptations. [1], [3]

Lagoon’s docs also note that Lagoon images are published with both :latest and versioned tags matching the Lagoon images release (e.g., :20.10.0), which is why :26.2.0 exists. [2]

Sources: [1] [2] [3]

🌐 Web query:

lagoon-images v26.2.0 release notes mysql-8.4 breaking changes

💡 Result:

lagoon-images v26.2.0 (released 2026-02-23) — MySQL-related notes

In this release, Lagoon updated the upstream MySQL base images, including:

  • mysql 8.4.8 (used by uselagoon/mysql-8.4) and mysql 8.0.45 (used by uselagoon/mysql-8.0). [1]

MySQL 8.4 breaking / behavior-changing items to watch for

When moving to MySQL 8.4.x (LTS), key breaking/impactful changes called out in Oracle’s 8.4.0 release notes include:

  • default_authentication_plugin is removed (use authentication_policy instead). Any configs still setting it will error on startup. [2]
  • The deprecated mysql_native_password plugin is disabled by default; if you still need it, you must explicitly enable it via --mysql-native-password=ON (or mysql_native_password=ON in config). [3]
  • Legacy replication terminology is removed/renamed: statements like START SLAVE, SHOW SLAVE STATUS, CHANGE MASTER TO, etc. are removed in favor of ... REPLICA ... / ... REPLICATION SOURCE ..., and several related Com_slave_* / Com_show_slave_* status variables are removed/renamed. [4]

Sources:
[1] lagoon-images 26.2.0 release notes (GitHub) [1]
[2] MySQL 8.4.0 release notes – removal of default_authentication_plugin [2]
[3] MySQL 8.4.0 release notes – mysql_native_password disabled by default [3]
[4] MySQL 8.4.0 release notes – replication statement/status-variable removals/renames [4]

Review MySQL 8.4 breaking changes before deploying this image.

The image tag uselagoon/mysql-8.4:26.2.0 is valid and published as part of lagoon-images v26.2.0 (Feb 23, 2026), which upgrades to MySQL 8.4.8. However, MySQL 8.4 introduces breaking changes that require configuration updates:

  • default_authentication_plugin is removed; existing configs using it will fail on startup.
  • mysql_native_password plugin is disabled by default; enable explicitly if required.
  • Legacy replication syntax is removed (START SLAVE → START REPLICA, CHANGE MASTER TO → CHANGE REPLICATION SOURCE TO, and associated status variables renamed).

Confirm your application and database configurations are compatible with MySQL 8.4.8 before merging.

🧰 Tools
🪛 YAMLlint (1.38.0)

[warning] 160-160: too few spaces before comment: expected 2

(comments)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@docker-compose.yml` at line 160, The selected DB image reference (IMAGE /
VORTEX_DB_IMAGE set to uselagoon/mysql-8.4:26.2.0) upgrades to MySQL 8.4 and
introduces breaking changes—inspect and update DB config and code to remove any
use of default_authentication_plugin, explicitly enable mysql_native_password
where clients require it, and replace legacy replication commands/status (START
SLAVE → START REPLICA, CHANGE MASTER TO → CHANGE REPLICATION SOURCE TO, and
renamed status variables) in any initialization scripts or orchestration logic;
if immediate compatibility cannot be ensured, change the IMAGE/VORTEX_DB_IMAGE
reference to a known-compatible older MySQL image or provide an override
mechanism until configs/code are updated.

environment:
<<: *default-environment
<<: *default-user
Expand Down