Skip to content

Update versioning policy to synchronize major and minor versions #2191

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

Open
David-Development wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update versioning policy to synchronize major and minor versions #2191

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
4 changes: 2 additions & 2 deletions VERSIONING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Versioning Policy

DevGuard uses a modified semantic versioning scheme: **all components share the same minor version**, but patch releases are independent per component.
DevGuard uses a modified semantic versioning scheme: **all components share the same major and minor version**, patch releases are independent per component.

## Compatibility Rule

Expand All @@ -15,7 +15,7 @@ DevGuard uses a modified semantic versioning scheme: **all components share the

## Rules

- **Minor versions are synchronized.** A feature release bumps the minor version across all components at the same time.
- **Major/Minor versions are synchronized.** A feature release bumps the major/minor version across all components at the same time.
- **Patch versions are independent.** A bug fix in only one component ships as a new patch for that component only — other components are not re-released.
- When upgrading, ensure all components share the **same minor version**. Patch versions do not need to match across components.

Expand Down
Loading