chore: release v0.7.105 - #3152
Merged
Merged
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Release v0.7.105.
User-facing change
Catalog search now understands meaning, not just keywords, and runs entirely on your machine (#3089). Finding the right block no longer depends on guessing its name.
Also: downloads follow every redirect a host may answer with (#3148), so fetches that previously died on a redirect chain now complete.
Observability correction (no behaviour change)
#3151 fixes two telemetry defects found while auditing the fast-capture dashboard. Neither changes how anything renders — only what renders report about themselves — but both were corrupting the data the drawElement roadmap is being planned from:
captureModereportedbeginframeon hosts that cannot run it. BeginFrame is Linux-only, enforced in both real entry points, but the observability field derived the mode fromforceScreenshotalone. That mislabelled 30,625 Windows renders over 14 days — about a fifth of the dashboard's capture-mode data — as BeginFrame when they were really screenshot.resolveDefaultDrawElementbranch returned a barefalse, and the orchestrator's clamp only fires whileuseDrawElementis still true, so a config-time refusal could never acquire a reason by construction. 56,507 renders over 14 days sat in the "Why not drawElement" chart's unnamed bucket. They now reportunsupported_platform,software_gpu,worker_encode_offordisabled.Worth knowing for anyone reading the fast-capture dashboard: the capture-mode field is now correct on non-Linux, but on Linux it remains an upper bound — the platform test is the only condition modelled, while real BeginFrame also needs a headless-shell binary, no supersampling, no transparent drawElement route and
--enable-begin-frame-control. Deriving the field from the session's ownlaunchCaptureModeis the tracked follow-up.Also in this release
Full changelog: v0.7.104...v0.7.105