chore(react): introduce changeset tool for change tracking

[danroberts]

A tool for managing a change log to the library

PR Checklist

• Important or complicated code is tested
• Any user facing changes are documented in the Gadget-side changelog
• Any immediate changes are slated for release in Gadget via a generated package dependency bump
• Versions within this monorepo are matching and there's a valid upgrade path

[MillanWangGadget]

Is there a way to make the created filenames based on timestamps? They're currently random word sequences that end up sorted in non-chronological order

Would it also be possible to automatically include the version number in the file contents?

[MillanWangGadget]

Is there are reason why these new Deps are added to the react package and not to the root? I was expecting to do pnpm changeset at the root, but am unable to since all of the changeset stuff is in the react package.

The CLI UI then asks about all of the packages in the repo

[danroberts]

I think the reason that the version number isn't in the changeset is because you could have several changesets in the same version. With this tool as I understand it, it will effectively bundle all the individual change files into one changelog, and it will suggest the new version number based on the minor/major changes involved

I don't think we want to track the changelog for all the packages in the repo, just for @gadgetinc/react for now.

[scott-rc]

LGTM 👍

I've had a good experience using changesets in ggt

[scott-rc]

nit: If you plan to have changesets release to npm then this will need to be public.

https://github.com/changesets/changesets/blob/main/docs/config-file-options.md#access-restricted--public