ci(P-4): bump pre-commit isort pin 5.13.2 → 8.0.1#42
Merged
Conversation
Aligns the pre-commit pin with what local Juniper conda envs ship (isort 8.0.1) and with juniper-canopy's pre-commit pin (already 8.0.1 since 2026-04-06's Phase 5 housekeeping). Previously, devs running ``isort`` directly from a Juniper conda env produced output that disagreed with what CI's pre-commit applied — see notes/POST_V38_OPEN_ISSUES_PLAN_2026-05-03.md (P-4), which traced two unnecessary CI iterations to this drift during the V38 diagnostic cycle. ``pre-commit run isort --all-files`` is clean against the new pin on this repo's tracked files, so this is a pure pin bump with no functional reformat.
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.
Aligns this repo's pre-commit isort pin with the local-Juniper-conda baseline (8.0.1) and juniper-canopy (8.0.1).
Closes the local-vs-pre-commit drift that caused two unnecessary CI iterations during V38 (juniper-ml notes/POST_V38_OPEN_ISSUES_PLAN_2026-05-03.md P-4).
pre-commit run isort --all-filesclean — pure pin bump, no reformat.