Closed AviVahl closed 3 weeks ago
Hi! When you fix this?
It can be easily fixed using https://docs.npmjs.com/cli/v10/commands/npm-dist-tag (has to be someone with publish access to the npm package)
@mmaietta any insights if this was intentional or can be rolled back? An -alpha
package is now marked as latest.
See #8241
Hmmmm, it should have occurred as the CI/CD has always published as next
only. Just reset latest
back to 24.13.3.
I'll look into the CI config, but it's already set to next
https://github.com/electron-userland/electron-builder/blob/29f6504e181cef2c43ac070a80f24ee79dc52481/packages/electron-builder/package.json#L71-L73
Thank you all for calling this out!
@mmaietta in #8253 same happened and electron-builder@25.0.0-alpha.10
is marked latest
.
Oh gosh darn it. I'll fix that asap. Not sure why the automation isn't working correctly now despite no changes. Thanks for the quick heads up!
Honestly, I have this same automation setup in app-builder repo and it works exactly as prescribed -> publishes all new releases as next
. IDK what's started happening here in this project since no CI/CD changes have occurred. I'll give it a go in updating pnpm and see if that resolves the issue
The new version was released as "latest", overriding the previous "24.13.3"
can also be seen on: https://www.npmjs.com/package/electron-builder?activeTab=versions