Add `changesets` for managing releases?

[TimMikeladze]

https://pnpm.io/using-changesets
https://github.com/changesets/changesets

This is a tool that assists in managing the release cycle for packages in a mono-repo. It will help with generating a changelog, creating github releases, git tags, etc.

[coyotte508]

Looks nice! As long as releases can be done directly from github actions like now

[pngwn]

Yes. There is a bot: https://github.com/apps/changeset-bot which is nice to help contributors add the correct files and an action: https://github.com/changesets/action which makes every CI driven.

It can also handle pre-releases although that is a touch more involved,

I've used changesets for a few years and found it really helpful for handling releases. I haven't set this up in a while but I'll be doing it for gradio soon, I don't mind having a go here too.

[o-az]

I'm happy to help with setting this up too! Been using changesets and it's very nice.

[coyotte508]

Sure!

For now we have two github actions, one for each package (could probably be reduced to one, with an additional parameter).

The github action bumps up the version, updates the docs, publishes to NPM and pushes the commit to the repo.

[pngwn]

Changesets is designed more multi package repos so should work fine ootb.

Changesets will create a 'version' PR that gets added to every time you merge to main. Merging that version PR will publish all necessary versions. It's nice in that the action never commits to main, just to a special branch that you then review + merge. I hate CI pushing directly to main, so I like this feature personally.

[coyotte508]

Sounds good!

[coyotte508]

current system works fine, if we have friction we may reopen

[coyotte508]

With @huggingface/widgets depending on tasks (and maybe later @huggingface/inference) and the multiple updates from various contributors, it may be worth it to switch to changesets now (or a similar system).

As long as the new system can still publish on both npm & github registries