chore: repair develop ancestry before v0.5.0 release - #28
Merged
Merged
Conversation
* feat: add deterministic Agentic EDA notebook export (#21) * fix: support pandas 3 datetime resolution in notebook export (#23) * feat: add human approval checkpoints for Agentic EDA (#22) * feat: add human approval checkpoints for Agentic EDA * fix: harden Agentic EDA approval validation * chore: prepare v0.4.0 release (#24)
suneelprojects
marked this pull request as ready for review
August 4, 2026 12:45
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.
Purpose
Repair
develophistory after PR #27 was squash-merged, preserving the code but discarding the intended two-parent ancestry.This PR reuses the already verified two-parent commit
66ca04c05a9610fe5ea716853a7268feb1b49fe2.Zero-code verification
develop:cffa0d3e9e461cb502f81c406a365dadc77d96d166ca04c05a9610fe5ea716853a7268feb1b49fe206a5b3e3b969c581d9aa3f25b9f378f1001f1872developand the repair head: 0 files6ac5c7dda47d63c996b01bf7d22981433c136e8b— v0.5.0develop5990735edd1dc7958f7ebb92e26f3b0223be499a— v0.4.0mainmainis already an ancestor of the repair head.mainis not yet an ancestor of currentdevelop.No source, test, documentation, version, or package file is changed by this repair.
Required merge strategy
Merge this PR using Create a merge commit only.
Do not use Squash and merge or Rebase and merge, because either would again discard the ancestry repair.
After merging, verify:
The command must exit successfully. Do not create the final
develop→mainrelease PR until that verification passes.