[maestrod] Update to 1.3.5 - #166
Open
olihou wants to merge 1 commit into
Open
Conversation
olihou
force-pushed
the
maestrod-1.3.4
branch
from
September 10, 2026 07:25
9e0327f to
b4f146b
Compare
olihou
changed the title
olihou
force-pushed
the
maestrod-1.3.4
branch
from
September 10, 2026 09:15
a67eb8d to
b4f146b
Compare
olihou
changed the title
fritznoff
approved these changes
Sep 10, 2026
Buildkite native-sdk-publish-daemon build 3433 published maestrod 1.3.5 from GdPicture master a750fbae. Supersedes the 1.3.4 bump this branch first carried; 1.3.4 never shipped. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
olihou
force-pushed
the
maestrod-1.3.4
branch
from
September 10, 2026 10:28
b4f146b to
3ca89be
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
2 participants
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.
Chart
0.6.8→0.6.9, appVersion1.3.3→1.3.5.1.3.5 comes from Buildkite
native-sdk-publish-daemonbuild 3433 —maestrod-version: 1.3.5, GdPicturemaster@a750fbae. Multi-arch amd64 + arm64 manifest pushed, release taggedmaestrod/v1.3.5.What 1.3.5 carries
One commit since 1.3.3's tip: PSPDFKit/GdPicture#3296, adding
VisionEngine.Auto = 3— a per-page router that estimates how much recognition power each page needs and sends clean pages to fast local extraction, harder ones to local ICR, and degraded or figure-heavy ones to VLM-enhanced ICR or the VLM pipeline. It is a new enum value: every existing engine, profile, and appsettings default is untouched, so no consumer changes behaviour without asking forAuto.(1.3.4 was built but never released; this goes straight from the deployed 1.3.3 to 1.3.5. The branch name predates that decision — GitHub won't let a PR change its head branch.)
Chart impact
None beyond the version numbers. No template, values, or schema change —
VisionEngine.Autois selected per request or through appsettings, neither of which the chart models.Worth knowing for whoever first enables
Auto: the router loads two encrypted ONNX models fromVision/DocRouting/(a frozen SigLIP2-large vision tower plus a small CORN head) throughIResourceDownloader.EnsureResourceAsync, so they are fetched at runtime unless staged underNATIVESDK_MODEL_RESOURCES. This chart has no volume or persistence support, so they land on the container filesystem and are re-fetched after every restart. Nothing to change today — no default selectsAuto— but it is the reason apersistenceblock may eventually be worth adding.Verification
README.mdis the helm-docs regeneration (helm-docs --chart-search-root charts/maestrod, v1.14.2), and thegeneratecheck passes. The CHANGELOG entry follows the existing per-release shape, with the TOC anchors shifted by one.Consumed by PSPDFKit/managed-cloud#334, which pins
0.6.9to take 1.3.5 to the stable GPU Maestrod in production.🤖 Generated with Claude Code