Replies: 1 comment
|
ℹ️ You can find a change log for every bugfix release here: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone,
we've got a change coming up that should make your life a bit easier: we're aligning the version numbers of all our bundles.
What's changing?
Starting with 2026.3.1, the first bugfix release of 2026.3, all bundles released on the same day will share the same version number, across all repositories. No more bundles drifting apart version-wise. One release day, one version number.
Heads-up: version jumps are normal now
We only release a bundle when something has actually changed in it. So you'll sometimes notice gaps in a bundle's version history.
Here's an example: Datahub is released as 2026.3.1. The next release, 2026.3.2, doesn't include any changes to Datahub, so there's no new Datahub version. When Datahub gets updates again, it's released as 2026.3.3. Its version history jumps straight from 2026.3.1 to 2026.3.3.
So if you spot a missing version number, don't worry. Nothing got lost or pulled back. That bundle simply had nothing new in that release.
Why are we doing this?
A single version number per release day makes it much easier to see which bundle versions belong together, to report and track issues, and to keep your installation consistent.
If you have questions, just let us know in the comments.
Thanks!
All reactions