When I tested the release with separate PRs, I saw that dependencies were being properly updated after a release. So for example, after merging the release PR for @eslint/core, release-please force-pushed a commit to the other PRs so that each dependent package would use the updated version of @eslint/core in their package.json files. I'm not sure why this didn't happen in this repo after merging #194. Maybe you were merging too fast? For example in #192, which is still unmerged, @eslint/core is correctly updated to 0.14.0.

This happened immediately upon merging #194 (I just didn't notice):
https://github.com/eslint/rewrite/actions/runs/14758801927/job/41433982243

Because npm run build builds all of the packages, when it tried to build @eslint/plugin-kit, it failed because it's package.json had not updated yet. To avoid that, #194 would have had to update all of the package.json files.

It's true, for some reason after @eslint/core was merged with #194 there was a force-pushed commit in #190 that switched back to using "@eslint/core": "^0.13.0" as a dependency in packages/plugin-kit/package.json.

-   "@eslint/core": "^0.14.0",
+   "@eslint/core": "^0.13.0",

https://github.com/eslint/rewrite/compare/33844b5b47e27905842340c6fb6a54698f51771e..a98b3a55561750f6e32c0b028f85a13e1a7776c0

It's not clear me why this happened.