Session 00KgRy4xOi5e

I can see issue #34 is the new publish issue for 3.0.4 (a new release was created that includes our fix). But I don't see the comment you linked — it might be on a failed workflow run. Let me check the workflow runs and the comment directly:

The publish failed again. Let me check the workflow run:

Let me see the rest of the logs to find the actual failure:

Found it. The corepack disable worked, but now npm install -g npm@latest itself is broken. The error is:

npm error code MODULE_NOT_FOUND
npm error Cannot find module 'promise-retry'

This is a known issue where npm install -g npm@latest corrupts itself mid-upgrade — npm 10.9.7 (bundled with Node 22.22.2) tries to install npm@latest (11.x) globally and breaks its own dependency tree in the process.

The real fix is to stop trying to self-upgrade npm and instead just use Node 24 which ships with npm 11.x natively. Let me also note the release/3.0.4 branch is what gets checked out — our fix needs to be there too.

The cleanest fix is to switch to Node 24 which ships with npm 11.x out of the box, eliminating the need for the npm upgrade step entirely. Node 24 ships with npm 11.4+ which fully supports OIDC trusted publishing.

Now let me push this fix. The publish workflow checks out the release/3.0.4 branch, but the workflow file itself is read from the default branch (since it's triggered by an issue label event). So pushing to master is sufficient.

Clean diff — switches to Node 24 and removes the broken npm self-upgrade step entirely.

PR created: https://github.com/BYK/superset/pull/35

Watching CI:

All green. Merging:

Merged. Now let me re-trigger the publish for 3.0.4:

Done. The publish workflow for 3.0.4 has been re-triggered. You can monitor it at https://github.com/BYK/superset/actions/workflows/publish.yml.

To recap what happened:

1. First failure: Corepack blocked npm because packageManager is set to pnpm -- fixed with corepack disable
2. Second failure: npm install -g npm@latest corrupts itself (MODULE_NOT_FOUND: promise-retry) when npm 10.x tries to self-upgrade to 11.x -- fixed by switching to Node 24 which ships with npm 11.x natively, removing the upgrade step entirely