Skip to content

doc,crypto: reorder ML-KEM in the asymmetric key types table - #60067

Merged
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
panva:doc-crypto-reorder-table
Oct 1, 2025
Merged

doc,crypto: reorder ML-KEM in the asymmetric key types table#60067
nodejs-github-bot merged 1 commit into
nodejs:mainfrom
panva:doc-crypto-reorder-table

Conversation

@panva

Copy link
Copy Markdown
Member

Order ML-KEM by security strength not by alphabetical order.

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/crypto

@nodejs-github-botnodejs-github-bot added crypto Issues and PRs related to the crypto subsystem. doc Issues and PRs related to the documentations. labels Sep 29, 2025
@lpinca

Copy link
Copy Markdown
Member

I think it makes sense to add a comment to prevent future alphabetical reordering.

@panvapanva added the author ready PRs that have at least one approval, no pending requests for changes, and a CI started. label Oct 1, 2025
@addaleaxaddaleax added the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 1, 2025
@nodejs-github-botnodejs-github-bot removed the commit-queue Add this label to land a pull request using GitHub Actions. label Oct 1, 2025
@nodejs-github-bot
nodejs-github-bot merged commit 3dc8c57 into nodejs:mainOct 1, 2025
31 checks passed
@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

Landed in 3dc8c57

@panva
panva deleted the doc-crypto-reorder-table branch October 3, 2025 06:49
targos pushed a commit that referenced this pull request Oct 6, 2025
PR-URL: #60067
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author readyPRs that have at least one approval, no pending requests for changes, and a CI started.cryptoIssues and PRs related to the crypto subsystem.docIssues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@panva@nodejs-github-bot@lpinca@addaleax