Version Overview and Release Policy¶
This page is the reference for how long a Gambio version is supported. It is updated with every release and is the page our terms and conditions, our mailings and our support team refer to.
If you want to know whether your shop is still covered, check your version in the Admin Portal and look it up in the table below.
Version overview¶
Status of the version lines¶
| Version line | Status | Security updates | Recommendation |
|---|---|---|---|
| Current (26.x) calendar-based, e.g. 26.09.0 |
Actively supported | Yes, ongoing | Stay current |
| v5.0.x | Phasing out | Until 31 December 2026 | Upgrade now |
| v4.x | Phasing out | Until 31 December 2026 | Upgrade now |
| v3.x and older incl. v2.x |
End of life | No security updates | Upgrade strongly recommended |
As of 14 September 2026. We announce changes here and in the forum in good time.
What the statuses mean¶
| Status | Meaning |
|---|---|
| Actively supported | The version receives security updates and new functionality. |
| Phasing out | The version still receives security updates until the date given. There is no further functional development. Plan your move. |
| End of life | No further security updates are published. The shop keeps running technically, but newly discovered vulnerabilities stay open. |
Release dates in detail¶
| Version line | First release | Last version | Succeeded by |
|---|---|---|---|
| 26.x | 26.03.0 · March 2026 | 26.09.0 | none |
| v5.0.x | 5.0.0.0 · 23 September 2025 | 5.0.2.0 · 26 January 2026 | 26.x |
| v4.x | 4.0.0.1 · 26 March 2020 | 4.9.6.1 · 11 August 2025 | 26.x |
| v3.x | 22 June 2016 | 20 February 2020 | v4.x |
| v2.x | 21 March 2011 | 10 June 2016 | v3.x |
Calendar-based versioning since March 2026
With 26.03.0 we moved to calendar-based version numbers: YY.MM.Patch. The year changes annually, but the line itself runs on continuously. The step from 26.12 to 27.01 is an ordinary update and not a version change. An individual monthly release is superseded by the next one and is not maintained separately.
Release management at Gambio¶
New versions are necessary to keep your shop legally and technically current: changing legal requirements, new PHP versions, payment and shipping providers, vulnerabilities in dependencies. We know that every update means effort on your side. That is why we keep releases small and predictable.
Version numbers¶
Since March 2026 the scheme is YY.MM.Patch, for example 26.09.0:
- YY: year of the release
- MM: month of the release
- Patch: a follow-up within the same month, for example
26.04.1
Up to and including GX5 a four-part number was used, following the pattern Major.Minor.Patch.Build, for example 4.9.6.1 or 5.0.2.0.
Types of release¶
| Type | What it contains | What it means for you |
|---|---|---|
| Master Update | Move to a new version line, new features, technical foundations | Largest effort. Themes and modules may need adjusting. Test it in a staging shop first. |
| Update Package | Combined update within a line, with features and bug fixes | Manageable. Testing recommended, usually no module changes needed. |
| Service Pack | Bug fixes and smaller improvements | Low. No changes to interfaces. |
| Security Patch / Security Update | Security-related fixes only | Install as soon as possible. Small and tightly scoped. |
You will find the installation paths for the update types under Installation.
Release cycle¶
- Regular release: monthly, at the beginning of the month
- Patch release: as needed, no fixed date
- Security patch: as soon as the fix is available
What a release changes¶
A breaking change is a change that requires adjustments to existing code so that modules and themes keep working. We avoid this within a line.
A deprecation announces that a function or interface will be removed in future. It still works in the current version but is marked for removal. If you maintain your own modules, this is your lead time for reworking them.
Support period¶
What support covers¶
In this overview, support means the technical maintenance of the software: fixing vulnerabilities and providing the corresponding updates. It does not mean a paid support and maintenance contract, and it does not mean further development with new features.
Security updates are always delivered in the current release. If your shop is behind, you get the fix by updating. A direct update to the current release is available from any version and is free of charge.
What happens after end of life¶
- No further security updates are released for the version.
- Newly discovered vulnerabilities remain open in that version.
- As the operator of your shop, Art. 32 GDPR requires you to take technical measures in line with the state of the art. A version without security updates does not meet that standard.
- The shop keeps running technically, but it is no longer secured.
Modules and interfaces
Third-party providers align their compatibility with the supported versions as well. Payment, shipping and marketplace integrations can stop working after end of life, without us being able to influence that.
What you can do now¶
- Check your version in the Admin Portal.
- Look it up in the table above to see how long your line is covered.
- Set up a staging shop and run the update there before you touch your live system.
- Clarify module and theme compatibility with your providers.
- Questions? Gambio Support.
Upgrading your licence to the current version is free of charge.