25.0.0-alpha.9 was released to npm as "latest"

[AviVahl]

The new version was released as "latest", overriding the previous "24.13.3"

$ npm dist-tags electron-builder
latest: 25.0.0-alpha.9
next: 25.0.0-alpha.8

can also be seen on: https://www.npmjs.com/package/electron-builder?activeTab=versions

[leevva]

Hi! When you fix this?

[AviVahl]

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)

[lutzroeder]

@mmaietta any insights if this was intentional or can be rolled back? An -alpha package is now marked as latest.

See #8241

[mmaietta]

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

electron-builder/packages/electron-builder/package.json

Lines 71 to 73 in 29f6504

	"publishConfig": {
	"tag": "next"
	}

Thank you all for calling this out!

[lutzroeder]

@mmaietta in #8253 same happened and electron-builder@25.0.0-alpha.10 is marked latest.

[mmaietta]

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

[mschoeffmann]

@mmaietta in #8253 same happened and electron-builder@25.0.0-alpha.10 is marked latest.

This is still happening, and sometimes in a big monorepo it causes v24 to be installed from one dependency and 25.0.0-alpha.10 from another ...

[mmaietta]

I don't believe so, looking at the release that was performed yesterday, it's correctly tagged as next
https://www.npmjs.com/package/electron-builder?activeTab=versions
https://www.npmjs.com/package/electron-updater?activeTab=versions

[mschoeffmann]

Indeed, now with v24.13.3 installed, it is pulling the same version as dependency again.
Before, I manually pinned app-builder-lib@24.13.2 and this solved it.

What happened to me in detail:
For the last months (on 24.13.2) everything was fine and without warnings.
Then, I think about 1-2 weeks ago, I started getting warnings after pnpm update about wrong versions of peer dependencies.
The warnings were about electron-builder-squirrel-windows@2.24.2 and electron-builder-squirrel-windows@25.0.0-alpha.10 were both installed.

pnpm why electron-builder-squirrel-windows showed something like:
electron-builder@24.13.2 depends on app-builder-lib@25.0.0-alpha.10 but also depends on electron-builder-squirrel-windows@2.24.2. And app-builder-lib@25.0.0-alpha.10 depends on electron-builder-squirrel-windows@25.0.0-alpha.10, which led to the conflict warnings.

This is based on what I remember, because now since the release of v24.13.3, I can not reproduce it any more.
Unfortunately I did not make any screenshots or logs, since I do not use electron-builder-squirrel-windows in that project and could quickly solving it by pinning app-builder-lib@24.13.2.

But since I found this issue here, I will pay attention if it happens again after pnpm update and keep you updated.

[mschoeffmann]

It happened again after pnpm update.
Here some more details, as promised:

my .npmrc:

engine-strict=true
auto-install-peers=true
shamefully-hoist=true
strict-peer-dependencies=false

a reduced package.json:

{
  "name": "TEST",
  "private": true,
  "engines": {
    "node": "^20",
    "pnpm": "^9"
  },
  "packageManager": "pnpm@9.4.0",
  "scripts": {
    "dev": "nuxi dev"
  },
  "devDependencies": {
    "electron": "^31.4.0",
    "electron-builder": "^24.13.3",
    "nuxt": "^3.12.4",
    "nuxt-electron": "^0.7.0"
  }
}

And the resulting pnpm-lock.yaml.txt.