Repository navigation
Mark the v0.6.0 and v0.6.1 decoding changes as breaking in CHANGELOG.md - #569
Merged
wojtekmach merged 1 commit intoOct 6, 2026
Merged
Conversation
Owner
|
Thank you for the PR. I agree it should have been marked appropriately. I am sorry for causing an incident. |
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
2 participants
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.
Two entries in the
CHANGELOG.mdchange default behaviour but don't specify them as breaking changes. We experienced a production incident related to this because we were relying on the default decompression and missed it as a potentially breaking change when bumping the dependency.This PR just makes it clear that the changes specifically in v0.6.0 and v0.6.1 are breaking changes that require action if the user is relying on automatic archive decoding (v0.6.0) or automatic decompression (v0.6.1).