Skip to content

tools: update OpenSSL on the selected branch - #66704

Open
panva wants to merge 1 commit into
nodejs:mainfrom
panva:openssl-workflow-dispatch
Open

panva wants to merge 1 commit into
nodejs:mainfrom
panva:openssl-workflow-dispatch

Conversation

@panva

@panva panva commented Oct 13, 2026 •

Copy link
Copy Markdown
Member

Use the selected workflow branch as the PR base and prefix PR titles for branches other than the repository's default branch.

This is in preparation for OpenSSL 4.1 update after which we need to be able to update versions prior to 27 with their respective OpenSSL series (3.5). This makes it so that we'll be able to do that with workflow_dispatch against the respective staging branch.

@panva panva added lts-watch-v22.x PRs that may need to be released in v22.x lts-watch-v24.x PRs that may need to be released in v24.x labels Oct 13, 2026
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

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

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Oct 13, 2026
Comment thread .github/workflows/update-openssl.yml Outdated
@panva panva added the commit-queue-squash PRs the Commit Queue should land as one squashed commit. label Oct 13, 2026
Comment thread .github/workflows/update-openssl.yml Outdated
Comment thread .github/workflows/update-openssl.yml Outdated
Comment thread .github/workflows/update-openssl.yml Outdated
Use the selected workflow branch as the PR base and prefix PR titles
for branches other than the repository's default branch.

Signed-off-by: Filip Skokan <panva.ip@gmail.com>
Assisted-by: Codex
@panva
panva force-pushed the openssl-workflow-dispatch branch from c99c81b to 5a33135 Compare October 13, 2026 12:48
@panva panva removed the commit-queue-squash PRs the Commit Queue should land as one squashed commit. label Oct 13, 2026
@panva panva added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Oct 13, 2026
@aduh95

aduh95 commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

Not sure we want the lts-watch-v22.x PRs that may need to be released in v22.x and lts-watch-v24.x PRs that may need to be released in v24.x labels, we expect to never have to run on those branches, no?

@richardlau

Copy link
Copy Markdown
Member

Not sure we want the lts-watch-v22.x PRs that may need to be released in v22.x and lts-watch-v24.x PRs that may need to be released in v24.x labels, we expect to never have to run on those branches, no?

Probably not, on the assumption we can run on for v26.x and cherry-pick the commits across.

@panva panva added the commit-queue PRs queued for automated landing through the Commit Queue. label Oct 13, 2026
@aduh95 aduh95 removed lts-watch-v22.x PRs that may need to be released in v22.x lts-watch-v24.x PRs that may need to be released in v24.x labels Oct 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs with CI started, the required approvals, and no outstanding review comments. commit-queue PRs queued for automated landing through the Commit Queue. 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.

4 participants