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
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 👍
The text was updated successfully, but these errors were encountered:
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 the0
major release every minor number is considered major so when someone defines^0.4
as a constraint you can't use0.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 released1.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 👍
The text was updated successfully, but these errors were encountered: