Maël Nison

> So such a single `yarn changeset` run results in a single changeset file containing release intents for N packages (they can have different bump types as described above) but...

Oh and, one problem that we currently have, it's sometimes a bit difficult for external contributors to know what to bump (for example that modifying the plugins require to mark...

We discussed with @Andarist and I think the takeaway was that we would want to uniformize the syntax used by Yarn and Changesets so that we'd still be able to...

> I don't think we should reinvent the wheel; do you have an RFC process set-up for Yarn Berry? It seems like we could start with an RFC and get...

> tools like `changesets` and `lerna` help with creating github tags (like `@namespace/[email protected]`). Basically, this can totally be done with a separate script for now, which I see you are...

Yes and no, the best would be to support reading both old and new format, and only generate new files with the new format. Differentiating the two at read time...

> This makes me wonder though, if we use their format, if only they expose their parser and logic for building the changelog, we can reuse those, otherwise we end...

It seems the failing tests are triggered by tau-prolog defining a global variable [the old way](https://github.com/tau-prolog/tau-prolog/blob/d03703a5a4144feb395083df80af7ec2a8a85f70/modules/core.js#L132), and Esbuild now adding `use strict` at the top of the generated bundle. I've...

> until fixed (by perhaps 2023?) Please learn how to interact professionally on open-source repositories. Being snarky makes me less likely to care about whatever problem *you* have and *I*...

Could we keep this version in a single place? Perhaps a `.node-build-version` at the root?