@developit good to see you outside of twitter :)

The way this PR is structured, our publishing scripts won't pick up anything for each plugin. It needs an upgrade to a more robust recognition of changes, and to take advantage of a new pnpm feature since it was written, but like all things I lack the time at the moment. With the one commit, none of the plugins will pick this up for publish until a commit targeting each plugin has been merged.

Regardless, this can play well with what we have, but the commits in this branch/PR need to be setup differently. We don't get these commits often (maybe 3 or 4 since the repo was conceived) so it hasn't been documented. Essentially, each plugin needs it's own commit. e.g. chore(auto-install): add directory to package.json. We'll then use a plain old merge commit for the PR and magically each plugin will see a change that'll allow us to run the publish scripts as they are. It's silly busy work, and I don't expect you to take the time to jump through that hoop. Without the hoop, you may not see your change for a bit in each plugin.

The choice is yours on which way to go with this, and we'll gladly accept either.

Welp, we'll merge this, but please be aware that it won't affect any plugins until they're published again. Which means most won't get this update published.