Skip to content

chore: recognize prefixed Node.js PR titles - #9925

Open
github-actions[bot] wants to merge 1 commit into
release/v11from
backport/v11/9915
Open

chore: recognize prefixed Node.js PR titles#9925
github-actions[bot] wants to merge 1 commit into
release/v11from
backport/v11/9915

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

Backport of #9915 to release/v11.

## Summary

- recognize existing Node.js npm update PRs with branch prefixes such as
`[v22.x]`
- preserve an existing PR title when updating it

## Background

The create-node-pr workflow successfully regenerated and force-pushed
nodejs/node#64884, but then failed because the existing-PR parser
treated `[v22.x] 10.9.9` as the npm version. It attempted to create a
duplicate PR instead of editing the existing one.

This extracts the version following the canonical `deps: upgrade npm to`
text regardless of any title prefix. Existing base-branch filtering
continues to distinguish PRs targeting different Node.js release lines.

Reproduction: https://github.com/npm/cli/actions/runs/32768286326

Copilot-Session: 14a9626a-4d0e-4be3-b06c-b6676ecb3895
(cherry picked from commit 81a901c)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant