Skip to content

tools: use different branch for tool updates on staging branches#63110

Open
aduh95 wants to merge 1 commit intonodejs:mainfrom
aduh95:tool-update-no-conflict
Open

tools: use different branch for tool updates on staging branches#63110
aduh95 wants to merge 1 commit intonodejs:mainfrom
aduh95:tool-update-no-conflict

Conversation

@aduh95
Copy link
Copy Markdown
Contributor

@aduh95 aduh95 commented May 4, 2026

To allow having concurrent update PRs for the same tool on different branches (e.g. Undici@6 version bump for v22.x-staging in #63109 was overwriting the Undici@8 for main in #63092).

The solution I went with is to add the base branch name in the PR branch name for non-main updates.

@aduh95 aduh95 added the lts-watch-v22.x PRs that may need to be released in v22.x label May 4, 2026
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/actions
  • @nodejs/security-wg

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label May 4, 2026
@aduh95 aduh95 force-pushed the tool-update-no-conflict branch from c959895 to 811d178 Compare May 4, 2026 08:31
@aduh95 aduh95 added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label May 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. lts-watch-v22.x PRs that may need to be released in v22.x meta Issues and PRs related to the general management of the project.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants