Re:Git-cliff – Generate changelog files from the Git history
by jameshart on Sunday September 05, 2021 @10:45AM
(#28424703)
I think it depends on the observable effect of the upgrade to a consumer of your component.
Did the dependency upgrade just improve performance? fix a bug? Add a new capability? Remove a backward compatible feature?
Certainly doesn’t automatically follow that if a dependency upgrade adds a feature, that that is a feature addition in your code, because you haven’t changed your code to use the new feature. But it could be - if you upgraded a parser library so it now supports strings longer than 4K, maybe your component now supports strings longer than 4K too and that merits a minor version bump.
It can be a pretty subtle judgement - especially with potentially deep dependency trees like are common in node.
If you’re bumping a dependency because the dependency has bumped one of its dependencies… can be tricky to figure out if there’s actually a noticeable effect.
Did the dependency upgrade just improve performance? fix a bug? Add a new capability? Remove a backward compatible feature?
Certainly doesn’t automatically follow that if a dependency upgrade adds a feature, that that is a feature addition in your code, because you haven’t changed your code to use the new feature. But it could be - if you upgraded a parser library so it now supports strings longer than 4K, maybe your component now supports strings longer than 4K too and that merits a minor version bump.
It can be a pretty subtle judgement - especially with potentially deep dependency trees like are common in node.
If you’re bumping a dependency because the dependency has bumped one of its dependencies… can be tricky to figure out if there’s actually a noticeable effect.