Skip to content

crypto: move DEP0203 and DEP0204 to End-of-Life#63188

Draft
panva wants to merge 1 commit intonodejs:mainfrom
panva:eol-DEP0203-DEP0204
Draft

crypto: move DEP0203 and DEP0204 to End-of-Life#63188
panva wants to merge 1 commit intonodejs:mainfrom
panva:eol-DEP0203-DEP0204

Conversation

@panva
Copy link
Copy Markdown
Member

@panva panva commented May 8, 2026

Moves support for passing CryptoKey instances to node:crypto APIs to End-of-Life status (DEP0203).

Moves support for passing a non-extractable CryptoKey instances to KeyObject.from() to End-of-Life status (DEP0204).

Closes #55293


doc-deprecation is since 24
runtime-deprecation is since 26
this eol is for 27

Moving DEP0204 to EOL in combination with the refactors done in #62924 and #63111 makes non-extractable CryptoKey instances actually non-extractable inside the Node.js process (barring --expose-internals 🤷‍♂️)

@panva panva added semver-major PRs that contain breaking changes and should be released in the next major version. deprecations Issues and PRs related to deprecations. labels May 8, 2026
@nodejs-github-bot
Copy link
Copy Markdown
Collaborator

Review requested:

  • @nodejs/crypto
  • @nodejs/userland-migrations

@nodejs-github-bot nodejs-github-bot added crypto Issues and PRs related to the crypto subsystem. needs-ci PRs that need a full CI run. labels May 8, 2026
Moves support for passing CryptoKey instances to node:crypto APIs to
End-of-Life status (DEP0203).

Moves support for passing a non-extractable CryptoKey instances to
KeyObject.from() End-of-Life status (DEP0204).

Closes nodejs#55293

Signed-off-by: Filip Skokan <[email protected]>
@panva panva force-pushed the eol-DEP0203-DEP0204 branch from b625ac4 to 3eb5d08 Compare May 8, 2026 09:18
@panva panva marked this pull request as ready for review May 8, 2026 09:18
@panva panva marked this pull request as draft May 8, 2026 09:29
@panva
Copy link
Copy Markdown
Member Author

panva commented May 8, 2026

Not wanting to cause unnecessary churn and cause backport needs for 26.x i'll leave this in draft form until we start with v27.x alphas.

@codecov
Copy link
Copy Markdown

codecov Bot commented May 8, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.06%. Comparing base (9adddc5) to head (3eb5d08).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #63188      +/-   ##
==========================================
+ Coverage   90.04%   90.06%   +0.01%     
==========================================
  Files         713      713              
  Lines      224926   224899      -27     
  Branches    42525    42527       +2     
==========================================
+ Hits       202526   202545      +19     
+ Misses      14180    14136      -44     
+ Partials     8220     8218       -2     
Files with missing lines Coverage Δ
lib/internal/crypto/keys.js 97.57% <100.00%> (+0.42%) ⬆️

... and 26 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

crypto Issues and PRs related to the crypto subsystem. deprecations Issues and PRs related to deprecations. needs-ci PRs that need a full CI run. semver-major PRs that contain breaking changes and should be released in the next major version.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Accepting CryptoKey in node:crypto APIs

2 participants