Repository navigation
docs: add the missing 1.0.1 changelog section - #270
Merged
Merged
Conversation
v1.0.1 (2026-06-15) was tagged but never got a CHANGELOG section. It fixed single-string config fields (id_columns="sku_num" etc.) being split into per-character tuples, which is not recorded anywhere else, and shipped the explicit outlier_action fix that is already described under 1.1.0.
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.
Summary
The
v1.0.1tag (2026-06-15) exists, butCHANGELOG.mdjumps from[1.1.0]straight to[1.0.0]. This adds the missing[1.0.1]section.id_columns="sku_num"became one entry per character, so ID protection,preserve_columns,duplicate_subsetandextra_sentinelssilently matched nothing. This fix (85761cd,tests/test_config_tuple_coercion.py) was not recorded anywhere in the CHANGELOG.outlier_action="cap"/"remove"fix (f7ac219) also shipped in 1.0.1. It is already described in full under[1.1.0], so the new section gives it one line pointing there rather than repeating it.Both commits are in
v1.0.0..v1.0.1. Docs only; no code changes.