Release Manager

Release workflow run: https://github.com/npm/node-which/actions/runs/18721020419

Release Checklist for v6.0.0

• 1. Approve this PR

  gh pr review 162 -R npm/node-which --approve

• 2. Merge release PR 🚨 Merging this will auto publish 🚨

  gh pr merge 162 -R npm/node-which --squash

• 3. Check For Release Tags

  Release Please will run on the just pushed release commit and create GitHub releases and tags for each package.

  gh run watch -R npm/node-which $(gh run list -R npm/node-which --workspace release -b main -L 1 --json databaseId -q ".[0].databaseId")

🤖 Created releases:

• v6.0.0

🌻

Release Workflow

• [email protected] https://github.com/npm/node-which/releases/tag/v6.0.0
• Workflow run: ✅ https://github.com/npm/node-which/actions/runs/18721186451

🚨🚨🚨

@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.

🚨🚨🚨

🚨🚨🚨

@npm/cli-team: The post-release workflow failed for this release. Manual steps may need to be taken after examining the workflow output.

🚨🚨🚨

This release failed to publish to npm. From reading the logs I'm not sure why, but could be a token issue or just a transient error.

If any token issues are fixed or the error is transient the workflow can be run again. If my memory is correct, the publish portion of the workflow is designed to be idempotent and can be run with a gh command like this:

gh workflow run release-integration.yml -R npm/node-which -f releases='[{"tagName":"v6.0.0","publishTag":"latest"}]'

Side note: the workflow was designed to ping the codeowners in the comment above which kinda worked. But it didn't actually ping the team. It's possible this is a bug in template-oss (Sorry about that 😄)

/cc @wraithgar @owlstronaut

In the past it has also worked to re-run failed jobs from the GH workflow UI itself. Trying that now from https://github.com/npm/node-which/actions/runs/18721186451

We migrated dozens and dozens of repos to oidc and only messed up on ONE of them getting the repo name right. This one. Fixed that and all is well now. Thanks @lukekarrys