What part of the version to change during major updates of internal dependencies?

Question

git

Good day! There is a module that connects to projects. Let's say the stable version at the moment is 1.2.5.
We go into package.json, we see that one of the dependencies is outdated, we update its version (for example, React 12.0.0 -> React 16.9.0 - the difference is 4 Major versions). At the same time, we do not touch the code of our module, nothing breaks, everything is "ok".
What version of our module should be now? 1.2.6? 1.3.0? 2.0.0?
Thanks

Answer 1

At the same time, we do not touch the code of our module, nothing breaks, everything is "ok".

And why update at the risk of getting along with backwards compatibility, without using the things that these updates give (for n major updates, I suppose there should be plenty of them)? As an option - do not roll out to the release until you write something new in terms of functionality so that you can justify changing the cyfor, and if the update is for the sake of updating, then install 1.2.6, and the default "bug fixes, security patch", for n-versions there obviously fixed something and protected something