docs(changelog): retroactively deprecate v1.3.0 and older due to config bug#17
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Roll Forward Deprecation Patch
This PR adds a retrospective deprecation warning to the
CHANGELOG.mdfor versionsv1.3.0and older.As mandated by the Tech Lead, these legacy versions contained a critical flaw in the bash wrapper that caused false-positive Exit 2 crashes by injecting an invalid
--configflag.This is a purely documentational patch targeting
mainand does not require a new tag. It will be naturally rolled into the next release.