I have a public project that I'm the single developer. I love updating packages to new versions regularly and keep the project up to date with the updated environment. This is probably not always a good approach as discussed in this question and this question , but I do it currently, because as I said , I love upgrading stuff.
The question is , when I update only the dependencies of a project, e.g. (
npm update) how should I change the SemVer versioning ? The updated packages does not add new features automatically to the business logic,so I believe no
major increase and just
increasing the patch ? On the other hand they make the program compatible with newer components or engines, and sometimes they fix bugs, so a
minor increase ?