Closed
Conversation
jmythms
force-pushed
the
dep_drift_unpinned
branch
from
21193fe to
345e575
Compare
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.
Experiment branch to test whether dependency drift causes integration results diffs.\n\nChanges:\n- Adds a no-op marker log line (DEP_DRIFT_TEST_MARKER)\n- Captures pip freeze --all into
esults/pip_freeze.txt (uploaded in artifacts)\n- Hardens diff/commit logic in integration workflow (no behavior change intended other than reliability)\n- Leaves Python deps unpinned\n\nNext: compare with pinned branch PR that uses constraints to Dec-2025 versions.