You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 2, 2025. It is now read-only.
I noticed that the upcoming minor version update includes breaking changes. According to Semantic Versioning guidelines, minor version bumps should only include backward-compatible additions, with breaking changes reserved for major version updates.
Including breaking changes in a minor release can disrupt dependent projects and workflows, as users typically expect minor updates to be safe to adopt without additional effort.
To ensure consistency and trust in versioning, could we improve the release process/documentation to better align with SemVer in upcoming releases?
I appreciate the team’s hard work on this project and want to help maintain its reliability for the community. Thank you for your time 🙇
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello maintainers,
I noticed that the upcoming minor version update includes breaking changes. According to Semantic Versioning guidelines, minor version bumps should only include backward-compatible additions, with breaking changes reserved for major version updates.
Including breaking changes in a minor release can disrupt dependent projects and workflows, as users typically expect minor updates to be safe to adopt without additional effort.
To ensure consistency and trust in versioning, could we improve the release process/documentation to better align with SemVer in upcoming releases?
I appreciate the team’s hard work on this project and want to help maintain its reliability for the community. Thank you for your time 🙇
The text was updated successfully, but these errors were encountered: