Repository navigation
vendor: model_compare.py v0.7.11 - #28
Draft
github-actions[bot] wants to merge 1 commit into
Draft
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
This branch has not been deployed
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
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.
Automated vendor bump opened by upgrade-pr.yml.
node scripts/sync-vendor.mjs v0.7.11rewrotevendor/model_compare.py(fetched at the tag's resolved commit) and re-pinnedvendor/UPSTREAM.json.Added lines touching imports / URLs / env vars / subprocess / file writes
sync-vendor output (sha change + upstream CHANGELOG section)
changed: sha256 3a96c11cc707… -> ac7cf1032c55…
[0.7.11] - 2026-11-20
Added
model-compare 0.7.11.FAQ — with refreshed navigation and page-specific assets.
catalog.jsonfiltered entries now carry AA quality and depth records, so--no-zdrruns are not quality-blind; unlabeled AA measurements display asunknownin the CLI tables,--depthsand the site tables.collisions merge automatically (keeping upstream's richer entry), genuine
price conflicts freeze and report per-key differences, and
web/litellm_collision_overrides.jsonrecords reviewed resolutions.litellm_merge_status.jsoncarriescollision_detailswith each key'sresolution, price equality and differing fields. The deduplicated issue
renders the same per-key price-difference table and closes itself after a
successful Pages deploy rebuilds the map.
Changed
litellmis pinned to 1.110.2 and thelitellm-compatgate runs onPython 3.15; Renovate keeps the job inside LiteLLM's
<3.16ceiling.LiteLLM artifacts.
Fixed
litellm-compatgate fails loudly when LiteLLM cannot be importedinstead of silently turning every compatibility test into a skip.
qualityandquality_matchnullness.