-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Open
Labels
Description
Logs: https://github.com/discordjs/discord.js/actions/runs/22245979203/job/64359888761
Running this locally with logs, I see this:
{
pkg: "@discordjs/docgen",
version: "0.12.1",
devTag: "dev",
timestamp: 1771638836,
commitHash: "77e767277",
}
ERR_PNPM_RECURSIVE_RUN_NO_SCRIPT None of the selected packages has a "release" script
79 | } else if (dry) {
80 | info(`[DRY] Bumping ${pkg.name} via git-cliff.`);
81 | release.version = `${pkg.version}.DRY-${devTag}.${timestamp}-${commitHash}`;
82 | } else {
83 | console.log({ pkg: pkg.name, version: pkg.version, devTag, timestamp, commitHash });
84 | await $`pnpm --filter=${pkg.name} run release --preid "${devTag}.${timestamp}-${commitHash}" --skip-changelog`;
^
ShellError: Failed with exit code 1
exitCode: 1,
stdout: " ERR_PNPM_RECURSIVE_RUN_NO_SCRIPT None of the selected packages has a \"release\" script\n",
stderr: "",
at new ShellPromise (75:16)
at BunShell (191:35)
at getReleaseEntries (/Users/jiralite/Documents/GitHub/discord.js/discord.js/packages/actions/src/releasePackages/generateReleaseTree.ts:84:11)
at async generateReleaseTree (/Users/jiralite/Documents/GitHub/discord.js/discord.js/packages/actions/src/releasePackages/generateReleaseTree.ts:140:29)
Even with @discordjs/docgen ignored, it's slipping through. Seems pnpm/pnpm#10437 has modified behaviour to cause this to fail. There are two solutions I see:
- Use
--if-present - Investigate why @discordjs/docgen is slipping through (seems to be the real fix)
Reactions are currently unavailable