got some CI issues there

It is so strange that the pnpm parallel execution in the ci fails...
On a local debian11 and windows10 machine the test runs even after clearing the cache.

I have a hope that it is a pnpm bug fixed in v8.7.6, will check tonight.

@lukastaegert i have that hope, too. I also think that in the pr #1595 it is the same problem.

@lukastaegert the --workspace-concurrency option, which i suggested for #1595 also solved the ci error here ^^. Maybe we can release this pr together with #1595

@shellscape i think this pr should be ready to merge.

I'm going to be working on the CI system here this week, and one that allows a wildcard scope so that any affected package is published. We've had to include a bananas-long ass scope too many times now. Once that's done we can merge this. I'll keep you posted.

I'm going to be working on the CI system here this week, and one that allows a wildcard scope so that any affected package is published. We've had to include a bananas-long ass scope too many times now. Once that's done we can merge this. I'll keep you posted.

Sounds good! Maybe Lerna is an option. I use it for many projects and it is pretty awesome 😌

Lerna is an absolute dumpster fire and the 2nd biggest pile of excrement for a devtool I've ever had the displeasure of using. It is only second to Nx in its awfulness. 😅

Working on this today. Have an elegant solution in mind.

Merged the update to the release pipeline but it needs an adjustment to account for the leading plugin- on the package names without the scopes. Will comment here once that's done. In the mean time, we should hold off on releasing anything. Should have that fixed this evening.

OK we're good to go

@tada5hi please update your branch from upstream/master

@shellscape i rebased the branch, but there seems to be an issue with the changed pr title.

I fixed that on master. We'll bypass that. Will pull the trigger on this tomorrow after noon ET when I can babysit releasing the freaking world 😅

should i rebase it again ?

We've got this #1618 PR for commonjs open which is going to be a breaking change/major, so I'd like to hold off just a bit on this one until we can get that resolved. I'll be trying to squeeze that change in without a release so we only get one major release for commonjs.