Latest Release on packages

[castrob]

Hi there,

Previously, when upgrading to the latest versions of the library, I would update every @codingame/monaco-vscode-** package. However, I noticed that the 33.X release did not include updates for all packages. Was this an intentional change?

Thanks!

[cookesan]

This can happen with the release flow.

The release script updates the package versions/dependencies to the release version and attempts to publish the generated packages. If npm reports that a package version already exists, that publish is skipped instead of failing the whole release.

So a 33.x release may show new publishes only for the packages that did not already have that exact version on npm. That does not necessarily mean every package changed in that release.

For consumers, the safest rule is still to keep the @codingame/monaco-vscode-* packages you use on the same release line/version where possible. If a package was not newly published for that tag, it may already have been present at that version.

[CGNonofr]

I did a lot of iterations to make the trusted publisher configuration work on every packages... it fails a few times, only the last 33.0.7 is working, previous 33.x versions are missing some packages

[CGNonofr]

Hum it looks like the 33.0.7 of @codingame/monaco-vscode-standalone-typescript-language-features is missing though 🤔

[CGNonofr]

Ok it looks like it's still not working 🤔 stay tuned

[CGNonofr]

Can you try again with the 33.0.9?

[castrob]

Hi! Thanks for the quick fix, it worked on 33.0.9, at least for the packages I'm using!