remove destroy_ events from list #37586
Merged
Conversation
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
mildwonkey
force-pushed
the
mildwonkey/destroy-events-never-heard-of-em
branch
from
e5976bd to
329762b
Compare
mildwonkey
added
the
no-changelog-needed
I expect these will come back, but since we don't have a firm roadmap just yet it's better not to make future promises.
mildwonkey
force-pushed
the
mildwonkey/destroy-events-never-heard-of-em
branch
from
329762b to
c11df4c
Compare
DanielMSchmidt
approved these changes
Sep 10, 2025
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.
I expect these will come back, but since we don't have a firm roadmap just yet it's better not to make future promises.
This removes the destroy_ events from the list of supported events and drops the diagnostic referencing their future implementation.
Fixes #
Target Release
1.14.x
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry