Revert: audit-fix merge (#11) — premature; code stays on dominik/audit-fixes-2026-05-28#12
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.
What this does
Reverts
dd40808— the merge of PR #11 (align Mahalanobis and DA PTP with manuscript; bump 0.8.0) — restoringmainto its pre-merge state at62e83b6.Why
The #11 merge was mis-targeted. The intent was to validate and merge revision PRs in a separate manuscript repository, not to land audit fixes on the public
kompotcode repo at this time. This revert backs the changes out ofmaincleanly.No code is lost. The full audit-fix changeset — B-001, B-002, M-003, N-001, plus the v0.8.0 version bump and
tests/test_audit_fixes.py— is preserved on the restored branchdominik/audit-fixes-2026-05-28(tip096fa2a5b) for continued use and a properly-targeted future merge.Reverted-merge gotcha (read before re-merging)
This is a revert of a merge commit. Git now records the audit-fix changes as "already present and then removed" along first-parent history. If
dominik/audit-fixes-2026-05-28is later re-merged intomainas-is, git will treat those changes as already-applied and silently drop them — the re-merge will appear to do nothing.To re-land the audit fixes after this revert:
git revert <this-commit>), then merge the branch; ormainso they arrive as fresh changes rather than through the already-reverted merge.This is the standard "reverting a merge, then re-merging" caveat (see git's
revertdocumentation / Linus's "How to revert a faulty merge" note).Scope
dd40808; nothing landed after it, so the revert applied with no conflicts.mainreturns to__version__ = "0.7.0"; the 0.8.0 bump stays on the restored branch.