⬆️ Bump Honeydiff to 0.11.1#301
Merged
Merged
Conversation
Update the CLI to the published Honeydiff 0.11 package and keep the first-party release-age exception narrow.
# Conflicts: # package.json # pnpm-lock.yaml # pnpm-workspace.yaml
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.
Why
The CLI should move to the same Honeydiff release Vizzly is consuming so local comparisons use the corrected 0.11 metric semantics plus the 0.11.1 hot-path recovery. This also avoids leaving the CLI on the older 0.10.3 package after the recovered release is public.
Approach
This updates the root dependency and pnpm lockfile to @vizzly-testing/honeydiff@0.11.1. The workspace release-age exemption moves to the exact fresh Honeydiff version so frozen installs can pass without relaxing the repo-wide supply-chain policy.
Evidence
The published package loads locally as 0.11.1 and exposes quickCompareSync. Pnpm accepts the frozen lockfile under the active supply-chain policy, and the CLI lint, type, comparison-service, comparisons command, and builds command coverage all still pass.