Repository navigation
Release sync v1.1.0 - #15
Draft
aurpsis-aai wants to merge 1 commit into
Draft
aurpsis-aai wants to merge 1 commit into
aurpsis-aai wants to merge 1 commit into
Conversation
Bump the sync stack to self-hosted-sync-asr-u3-pro:release-v1.1.0, built from DeepLearning dbfd4bbf. The license-and-usage-proxy is unchanged and stays at release-v1.0.0, so the Modal app's single TAG splits into SYNC_TAG/PROXY_TAG. Document what changed since v1.0.0: compressed audio, opt-in word timestamps, 13 more languages, GET /warm, the /v1 route prefix, and keyterms_prompt as the preferred name for the keyterms list. Correct three statements in the sync README that no longer hold: MP3 is now accepted rather than rejected with 415, unknown config fields are now rejected with 400 rather than silently ignored, and the keyterms field is documented under its current name with its aliases. Word timestamps need SYNC_BFA_ALIGNMENT_ENABLED on the sync-api container. The alignment checkpoint ships in the image, but the flag defaults off, so a `timestamps: true` request otherwise returns words with no start/end and no warning. Plumb the flag through compose and the Modal app so it can be turned on from .env. Validated on a GPU host against release-v1.1.0 with IMDS disabled: both prefixed and unprefixed routes, 401 without an Authorization header, MP3, keyterms_prompt/word_boost equivalence, the multi-alias 400, unknown-field 400, word timestamps once the flag is on, and usage reporting reaching the usage-tracker as sync_transcription_self_hosted. Co-Authored-By: Claude Fable 5 (Jeeves) <noreply@anthropic.com>
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.
Bumps the self-hosted sync stack to
self-hosted-sync-asr-u3-pro:release-v1.1.0, cut from DeepLearningdbfd4bbf(release run). v1.0.0 was cut 2026-06-30; 39 commits have landed inasr_sync_u3prosince.license-and-usage-proxyhas no commits since the v1.0.0 image and stays atrelease-v1.0.0. The Modal app used one sharedTAGfor both images, so it splits intoSYNC_TAG/PROXY_TAG.Why 1.1.0 and not 2.0.0
The three changes that look breaking aren't:
/v1prefix —app.pymounts the router both prefixed and unprefixed; existing clients keep working.word_boost→keyterms_prompt—word_boostandkeytermsare still accepted as aliases. Only internal analytics fields were renamed./transcribe/stream→/transcribe/live— that route landed after the v1.0.0 image, so no v1.0.0 user ever had it.The one genuine behavior change is that unknown
configfields are now rejected with400instead of ignored. Called out under "Behavior change" in the changelog.Documentation corrections
Three statements in the sync README were wrong as of this image:
415; compressed audio (AAC, MP3, M4A, OGG, WebM, FLAC) is now accepted.400. This one was actively misleading.word_boost.Word timestamps need a flag
timestamps: trueis accepted and returns200, butSYNC_BFA_ALIGNMENT_ENABLEDdefaults tofalseand the aligner's init returns silently when it's off — so words come back with nostart/endand nothing in the logs says why. The checkpoint ships in the image; only the flag was missing from the self-hosted stack (production terraform already sets it). Plumbed through compose,.env.example, and the Modal app.Validation
Run on a GPU host against
release-v1.1.0withAWS_EC2_METADATA_DISABLED=true, so instance-role credentials couldn't mask a customer-environment auth failure:/transcribeand/v1/transcribe200Authorizationheader401200keyterms_promptvsword_boost400, names the conflict400timestamps: true, flag off200, nostart/endtimestamps: true, flag onstart/endpopulated; aligner loads and warmsGET /warm200 {"warm":"toasty"}sync_transcription_self_hosted,200The last row is the v1.0.0 billing gap closing: those reports were rejected then, which on a usage-based license also crash-looped the proxy.
🤖 Generated with Claude Code