chore: fix changelog after automation error

[pauldambra]

CD task was broken because of linting which meant we never published 1.202.3 and 1.202.4 is mungled up with 1.202.5

this updates the changelog to represent what is in each release

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
posthog-js	✅ Ready (Inspect)	Visit Preview	Dec 19, 2024 3:21pm

[rafaeelaudibert]

Was 1.202.4 published? If not, we could simply put all of this inside 1.202.3 instead

It's terrible that npm allowed us to publish 1.202.4 without publishing 1.202.3

[github-actions]

Size Change: 0 B

Total Size: 3.22 MB

ℹ️ View Unchanged

Filename	Size
dist/all-external-dependencies.js	206 kB
dist/array.full.es5.js	262 kB
dist/array.full.js	365 kB
dist/array.full.no-external.js	364 kB
dist/array.js	179 kB
dist/array.no-external.js	178 kB
dist/customizations.full.js	12.6 kB
dist/dead-clicks-autocapture.js	14.4 kB
dist/exception-autocapture.js	9.48 kB
dist/external-scripts-loader.js	2.48 kB
dist/main.js	180 kB
dist/module.full.js	365 kB
dist/module.full.no-external.js	364 kB
dist/module.js	179 kB
dist/module.no-external.js	178 kB
dist/recorder-v2.js	115 kB
dist/recorder.js	115 kB
dist/surveys-preview.js	57.6 kB
dist/surveys.js	63.3 kB
dist/tracing-headers.js	1.76 kB
dist/web-vitals.js	10.4 kB

_{compressed-size-action}

[pauldambra]

Was 1.202.4 published? If not, we could simply put all of this inside 1.202.3 instead

yep, 1.202.3 was never published, 1.202.4 was published but the automation that updates the changelog can't cope with anything but a clean set of releases (it doesn't even cope with two merges too close together 🙈)

It's terrible that npm allowed us to publish 1.202.4 without publishing 1.202.3

they only enforce that you don't try and publish a duplicate iiuc