feat(node): disable immediate data deletion after BlobDeleted events by default#3161
Merged
halfprice merged 3 commits intoreleases/walrus-v1.44.0-releasefrom Mar 19, 2026
Merged
Conversation
Contributor
|
Warning: This PR modifies one of the example config files. Please consider the
|
e50fa85 to
9bca919
Compare
1 task
halfprice
approved these changes
Mar 19, 2026
83a4e03
into
releases/walrus-v1.44.0-release
23 of 24 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Cherry-picks #3160 into the v1.44 release.
Test plan
See #3160.
Release notes
garbage_collection.enable_immediate_data_deletion, which defaults tofalse. When processing aBlobDeletedevent, data is only deleted immediately if this parameter is set to true.