Skip to content
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

Consider releasing a 1.0 version #20

Open
stayallive opened this issue Apr 12, 2024 · 0 comments
Open

Consider releasing a 1.0 version #20

stayallive opened this issue Apr 12, 2024 · 0 comments

Comments

@stayallive
Copy link

stayallive commented Apr 12, 2024

Hey @valorin,

You just pushed an update for require-dev (which I don;t think you would even need to release but that is besides the point). This feels like it could have been a minor update. But because you are on the 0 major release every minor number is considered major so when someone defines ^0.4 as a constraint you can't use 0.5 because that is considered the next major so when a package uses your package as a dependency they now need to update their dependencies to ^0.5 to prevent running an "outdated" version.

If you are on 1.0.0 you could've released 1.1.0 and the ^1.0 constraint would work just fine and no need for upstream packages to update their requirements.

Not a super big deal obviously because I just also just couldn't depend on a pre-release package but for your consideration 👍

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

No branches or pull requests

1 participant