Today we have the situation where if ONE plugin has a problem, it breaks the whole multi-semantic-release (MSR) release process.

We don't have an easy way to manually release a single dependency like shared-react so that other projects can depend on its newer version.

One idea might be to write a script that uses semantic-release in a for-loop using the --ci false flag to avoid the requirement to be run inside a CI process (eg., GH action).

https://github.com/semantic-release/semantic-release/blob/HEAD/docs/usage/configuration.md#configuration

This might allow us to do something like:

yarn build --filter=shared-react
npm config set workspaces-update false

export NPM_TOKEN=npm_***
export GITHUB_TOKEN=****
yarn --cwd plugins/shared-react/ release --ignore-private-packages --filter=shared-react --ci false

in a for loop for each of the plugins we want to release (or check if they need releasing)