Skip to content

Dependencies: Restrict dependency version requirements #325

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.

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 1 commit into from
Feb 26, 2024

Conversation

sphuber
Copy link
Collaborator

@sphuber sphuber commented Feb 26, 2024

Packages that have a major release of v1 or higher are expected to maintain semantic versioning and so packages are pinned to the major version. Packages that haven't seen a v1 release yet, are pinned to the minor version instead, as they are more likely to break backwards compatibility in minor releases.

Packages that have a major release of v1 or higher are expected to
maintain semantic versioning and so packages are pinned to the major
version. Packages that haven't seen a v1 release yet, are pinned to the
minor version instead, as they are more likely to break backwards
compatibility in minor releases.
@sphuber sphuber merged commit 04e11ef into master Feb 26, 2024
@sphuber sphuber deleted the fix/restrict-dependencies branch February 26, 2024 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant