mirror of
https://github.com/semver/semver.git
synced 2026-03-22 14:10:15 -05:00
Addition of a schema for a better understanding of semantic versioning #660
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#660
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @vianneyyovo on GitHub (Feb 9, 2025).
The article is very clear on the principles of semantic versioning, but it could be made even more accessible with concrete examples from well-known projects (e.g. Node.js, React, Linux). Adding a section on enterprise best practices, such as integration with CI/CD or dependency management, would make the document even more useful for developers and technical teams.
And also proposing a visual diagram illustrating the evolution of a software version according to the principles of semantic versioning could make the article more accessible. For example, a timeline diagram showing the evolution of an application from version 1.0.0 to 2.0.0, with intermediate steps (1.1.0, ...), would enable readers to better understand how to apply these rules in a real project.