new stable release v13.0.0

[gnapse]

Now that Reactist is back to having all the new changes in a stable non-beta release (v25.0.0), this pull request brings that Reactist version to the ui-extensions, and brings this repo's recent changes in next back to main.

This pull request will be released as a new version v13.0.0 of the ui extensions react package.

[gnapse]

Now, after having made the peer dependency change, there's a failed check in CI. Though, it does not look related to the peer dependency change. It's an npm audit warning about the package braces. 😕

---

Update: it does have to do with the change to peer dependency. What happens is that we have a CI step that runs npm run audit --omit=dev. When Reactist is a dev dependency, it is not being included in this check. But when it switches to be only a peer dependency, it is part of this check.

However, I'm still confused. This braces dependency does not seem to be introduced by Reactist (see screenshot below). So I'm not sure how excluding Reactist from the dev dependency suddenly surfaces this warning.

Screenshot

Anyway, I'm going to revert the change to make Reactist a peer dependency only. We can revisit this soon, but I need to be unblocked now.

[gnapse]

@scottlovegrove what's the procedure to release? I assume that after merging I need to do something else, but I'm not sure. I also did not find anything in the README about it.

[scottlovegrove]

@scottlovegrove what's the procedure to release? I assume that after merging I need to do something else, but I'm not sure. I also did not find anything in the README about it.

It just needs a new tag creating once the PR is merged to main. Tag should be react-v<number>

I should add that to the readme 👍🏻

[gnapse]

I assume the by "a new tag" you mean "a new release" in https://github.com/Doist/ui-extensions/releases, which creates a new tag, and also has a description, etc. I'll create it.