Support MySQL 26.x (new calendar-based versioning)

Open
#142 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
java, mysql
Domain
databases

Research direction

Start by locating Databus's MySQL version check and parsing logic, since the issue does not name specific files or tests. Trace how supported major versions are determined, then verify that MySQL 26.x examples such as 26.7.0 and 26.10.0 are accepted without breaking existing 5.x, 8.x, and 9.x handling.

Written by the indexing model from the issue text.

Description

Summary

MySQL has switched to calendar versioning (CalVer) starting with version 26.7 (July 2026), replacing the previous 8.x/9.x sequential scheme. Version numbers now follow YY.M.P (e.g. 26.7.0, 26.10.0).

Databus currently reports:

  • unsupported MySQL major version: 26 (supported: 5.x, 8.x, 9.x)

Question

  • Is support for MySQL 26.x (and future CalVer releases) planned?
  • If not yet planned, would a PR be welcome? Any guidance on where the version check/parsing logic lives would help.

Reference

https://dev.mysql.com/doc/refman/26.7/en/mysql-releases.html

Dominant language
Java
Stars
3.7k
Forks
734
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from linkedin/databus

All issues in linkedin/databus

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.