Skip to content

Update the versioning section #2034

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
merged 4 commits into from
Jan 9, 2025
Merged

Update the versioning section #2034

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fa88268
Update the versioning section
renetapopova Jan 2, 2025
1dd36e2
Update modules/ROOT/pages/introduction.adoc
renetapopova Jan 9, 2025
5ca78e0
Update modules/ROOT/pages/introduction.adoc
renetapopova Jan 9, 2025
3eb72c5
Update modules/ROOT/pages/introduction.adoc
renetapopova Jan 9, 2025
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
16 changes: 10 additions & 6 deletions modules/ROOT/pages/introduction.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -285,11 +285,15 @@ For more information about what data is collected, see link:https://neo4j.com/do
[[versioning]]
== Versioning

Neo4j uses semantic versioning (link:{semver-uri}[Semantic Versioning Specification 2.0.0]).
Given a version number `MAJOR.MINOR.PATCH`, the increment is based on:
2025.01.0 introduces a new calendar versioning (CalVer) for the Neo4j server instead of the previously used semantic versioning (SemVer).
The new versioning format, *YYYY.MM.Patch*, is based on the year and month of the release, for example, 2025.01.0, 2025.02.0, and so on.
The patch number is incremented for each release within the same month.

* `MAJOR` version - incompatible API changes towards the previous `MAJOR` version.
* `MINOR` version - functionality in a backward-compatible manner.
* `PATCH` release - backwards-compatible bug fixes.
Some of the releases will be designated as long-term support (LTS) releases.

Neo4j’s fully managed cloud service link:{aura-uri}[Neo4j Aura] uses only `MAJOR` versioning.
link:{aura-uri}[Neo4j Aura] always uses the latest version of the Neo4j server.

== Operations Manual versioning

The Operations Manual is versioned according to the calendar version of the Neo4j server.
For example, the Operations Manual for Neo4j 2025.01.0 is versioned as 2025.01.0 and reflects the features and changes in that release.
Loading