Please be mindful of version bounds and semantic versioning when tagging your packages

[fredrikekre]

@chakravala

You are wrong, I have previously tagged releases in the new registry and have seen what happens.

What happens is that in the registry all previous version get the bounds added. Try it, you’ll see.

Since the registry entries get updated, when somebody updates their registry, they get the bounds.

I’m not wrong.

@chakravala

By doing tests and taking a look at the breaking changes to see what changed.

But there is nothing to test, there is no new release to test against.

@chakravala

That’s the whole point… you are just guessing, which is reckless. You literally want people to guess when there might be an incompatibility. This is to me the definition of reckless and careless.

I mean, it’s a qualified guess. The only logical guess. We have to assume that if the package author releases a breaking (according to semver version) release it will break our package.

Whats so terrible with actually waiting and testing against the new release when it is released?