Support MySQL 26.x (new calendar-based versioning)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from linkedin/databus
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
-
gguugOpen
Difficulty 5/5 Over a week Newbie friendliness 1/100
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
All issues in linkedin/databus
Similar issues
-
JPA security login throws when the stored password or roles string is nullPossibly taken @SebTardif claimed this today. Openarea/security env/windows
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
quarkusio/quarkus#58548 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
microsoft/copilot-for-eclipse#522 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
marchof/java-almanac#354 ·
-
bug posit-ai
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day