Should I Bump Up My Version for Removing a Dependency?

0
0
Asked By CuriousCoder42 On

I'm working on an issue for *Spectre*, a Python tool for recording radio spectrograms. The goal is to remove Scipy as a dependency from the package *spectre-core*. My recent pull request didn't change anything in the public API; it just reimplemented functionality specific to our needs without Scipy. Since I'm following semantic versioning, I'm unsure if I should classify this change as a major, minor, or patch version bump. I thought about bumping it to major since users depending on Scipy as a transitive dependency might see this as a breaking change. However, since that functionality isn't exposed publicly, I think a minor bump might suffice. What do you all think?

5 Answers

Answered By DependencyDynamo On

Removing a dependency usually leans towards a patch version since it simplifies things for users. If someone is relying on Scipy via your package, that's more on them, right? If your change turns it so that Scipy can't even be installed anymore, then that's a major change.

CodeNinja77 -

Totally agree! Users can always add it back if needed. A patch increment makes the most sense here.

Answered By SemanticSam On

I think most responses here are spot on - it should be a patch since it's similar to removing private functions. If anyone relies on that behavior, they should manage it as their own dependency. But still, a minor bump could gather some attention to the update.

Answered By ReleaseManager101 On

Personally, I think this shouldn't even trigger a release. If the only reason is removing a dependency, it might not count as a significant improvement for users. Just wait for the next actual feature and bundle it with that release.

TechieChick -

But removing dependencies does make a package easier to use! It's a valid reason to release, even if it's just a patch or minor bump.

Answered By VersionGuru93 On

Yeah, it's definitely a patch in terms of semantics, but I’d personally aim for a minor bump too. It keeps things in line with best practices.

Answered By CodeMaster6 On

I stand by the idea that semantically it qualifies as a patch. If users rely on that package, they should declare it as needed! However, considering the context, a minor release might encourage easier adoption by consumers.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.