Follow semantic versioning for NPM packages

[kjetilk-kontali]

Is your feature request related to a problem?

Proper SemVer versioning

Describe the solution you'd like

It's annoying that you use the 'minor' version for patch upgrades. E.g., version 1.360.0 (minor version 360) is a patch release - not a minor version up.

Describe alternatives you've considered

Follow semantic versions (like "everyone" else)

[pauldambra]

hey, we do!

in this case our core types had a minor version bump and posthog-js had two fixes and they were combined into a minor version bump

it is a consequence of not releasing every change we make by default - since we've had feedback from others that releasing too frequently was a problem for them

i sort of hate the changelog library we use because it doesn't make the core package dependency update particularly clear

out of interest, what was the friction for you here?

[kjetilk-kontali]

The friction is exactly what you mentioned; Too many updates, but more importantly it's hard to know if this is a upgrade I really need.

I think 360 minor versions is a tell. There's just no way that there could be 360 recommended upgrades of this package. Does a minor version up on a dependent package really justify a minor on posthog-js? Is there a notifiable change that I miss if I don't upgrade here? Or is it just a patch when looking at it from the posthog-js side of it?

[pauldambra]

for our automation it isn't a patch release :)

@dustinbyrne you have the context on whether treeshakeable should have been patch or minor
(and whether there's anything the changelog package would have let us do here)

[kjetilk-kontali]

for our automation it isn't a patch release :)

Exactly. So my request is really that you follow SemVer. Hence; For me as an end user of the posthog-js does e.g. "treeshakeability" (or the other 359 minor upgrades) really add any functionality for me? Does it effect the result in the PostHog analytics? If so it should be stated in the release notes that "this minor release adds X functionality in PostHog". If it doesn't I would say that this is a patch - not a minor version.

[dustinbyrne]

Regarding v1.360.0 specifically, I'd have expected it to be released as v1.359.2 given it didn't contain a minor change to the posthog-js package itself, but was still released as a minor change.

Perhaps it's somehow inherited the minor version bump from @posthog/types given they were released at the same time. Even the changelog states it was a patch, so I'll take a deeper look into this.

Thanks for raising this!