stream: skip null output from stateful transforms by trivikr · Pull Request #64462 · nodejs/node

trivikr · 2026-07-12T20:23:40Z

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

trivikr · 2026-07-12T20:23:40Z

Fixes: #64461

Stateful transforms currently pass null output to the flattening
helpers, causing ERR_INVALID_ARG_TYPE. Transform output
normalization defines null as no output.

Skip null before flattening stateful transform output in both the
sync and async paths.

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot · 2026-07-12T20:23:44Z

Review requested:

@nodejs/streams

nodejs-github-bot · 2026-07-12T21:25:28Z

CI: https://ci.nodejs.org/job/node-test-pull-request/74768/

codecov · 2026-07-12T22:15:41Z

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (14166a5) to head (3c2ae5a).
⚠️ Report is 111 commits behind head on main.

Additional details and impacted files

@@ Coverage Diff @@## main #64462 +/- ##
==========================================
+ Coverage 90.23% 90.67% +0.43% 
==========================================
Files 741 744 +3 Lines 241375 245072 +3697 Branches 45483 50711 +5228 ==========================================
+ Hits 217800 222207 +4407 + Misses 15129 14459 -670 + Partials 8446 8406 -40

Files with missing lines	Coverage Δ
lib/internal/streams/iter/pull.js	`83.89% <100.00%> (+0.03%)`	⬆️

... and 105 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.

Renegade334 · 2026-07-16T13:59:16Z

I was under the impression that stateful transformers should not be yielding null at all, they should just mark the iterator as done to mark end-of-output?

trivikr · 2026-07-20T05:10:40Z

stateful transformers should not be yielding null at all

A null output is accepted as per specification §9.3 Transforms

Transform return values are flexible. A transform may return: null (no output), Uint8Array[] (a batch), a single Uint8Array, a USVString (UTF-8 encoded), an iterable or async iterable (flattened), or a promise (awaited, async only).

And the bug is explained in #64461

@Renegade334 Would you like to create an issue on the specification?

I don't see a block from you, but I've removed author-ready.
I'll re-add it and land the fix based on your response.

nodejs-github-bot · 2026-07-23T23:32:19Z

Landed in 68dc116

Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com> PR-URL: #64462Fixes: #64461 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Ethan Arrowood <ethan@arrowood.dev>

stream: skip null output from stateful transforms
3c2ae5a
Treat null yielded by sync and async stateful transforms as no output, consistent with transform normalization semantics. Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>

nodejs-github-bot added needs-ci PRs that need a full CI run. stream Issues and PRs related to Node.js streams. labels Jul 12, 2026

trivikr added the request-ci Add this label to start a Jenkins CI on a PR. label Jul 12, 2026

jasnell approved these changes Jul 12, 2026
View reviewed changes

github-actionsBot removed the request-ci Add this label to start a Jenkins CI on a PR. label Jul 12, 2026

trivikr added the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Jul 12, 2026

trivikr removed the author ready PRs with CI started, the required approvals, and no outstanding review comments. label Jul 20, 2026

trivikr marked this pull request as draft July 22, 2026 05:19

This comment was marked as outdated.
Sign in to view

trivikr marked this pull request as ready for review July 23, 2026 13:03

trivikr added commit-queue PRs queued for automated landing through the Commit Queue. and removed commit-queue PRs queued for automated landing through the Commit Queue. labels Jul 23, 2026

Ethan-Arrowood approved these changes Jul 23, 2026
View reviewed changes

trivikr added the commit-queue PRs queued for automated landing through the Commit Queue. label Jul 23, 2026

nodejs-github-bot removed the commit-queue PRs queued for automated landing through the Commit Queue. label Jul 23, 2026

nodejs-github-bot merged commit 68dc116 into nodejs:mainJul 23, 2026
128 of 129 checks passed

aduh95 mentioned this pull request Jul 30, 2026
2026-07-22, Version 26.6.0 (Current) #64655
Merged

trivikr deleted the stream-iter-stateful-stream-transform-null branch July 31, 2026 04:31

github-actionsBot mentioned this pull request Aug 21, 2026
2026-08-26, Version 24.20.0 'Krypton' (LTS) #65461
Merged