v6 betas are published as `latest` on npm

[kachkaev]

I've noticed that 6.0.0-beta.1 for @rjsf/core, @rjsf/mui, etc. is latest:

This means that npm install @rjsf/core resolves to 6.0.0-beta.1 instead of 5.24.10.

Until v6 has reached stability, I suggest modifying dist-tags on npm:
https://docs.npmjs.com/cli/v11/commands/npm-dist-tag

Example:

npm dist-tag add @rjsf/core@6.0.0-beta.1 canary
npm dist-tag add @rjsf/core@5.24.10 latest

You don't need to re-publish packages to do this.

[nickgros]

I don't think I have permission to do this from the CLI, so we'd have to update our workflows to fix this