Skip to content

Release sync v1.1.0 - #15

Draft
aurpsis-aai wants to merge 1 commit into
mainfrom
aurpsis/sync-release-v1-1-0
Draft

aurpsis-aai wants to merge 1 commit into
mainfrom
aurpsis/sync-release-v1-1-0

Conversation

@aurpsis-aai

Copy link
Copy Markdown
Contributor

Bumps the self-hosted sync stack to self-hosted-sync-asr-u3-pro:release-v1.1.0, cut from DeepLearning dbfd4bbf (release run). v1.0.0 was cut 2026-06-30; 39 commits have landed in asr_sync_u3pro since.

license-and-usage-proxy has no commits since the v1.0.0 image and stays at release-v1.0.0. The Modal app used one shared TAG for both images, so it splits into SYNC_TAG / PROXY_TAG.

Why 1.1.0 and not 2.0.0

The three changes that look breaking aren't:

  • /v1 prefix — app.py mounts the router both prefixed and unprefixed; existing clients keep working.
  • word_boost → keyterms_prompt — word_boost and keyterms are 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 config fields are now rejected with 400 instead of ignored. Called out under "Behavior change" in the changelog.

Documentation corrections

Three statements in the sync README were wrong as of this image:

  • MP3 was documented as rejected with 415; compressed audio (AAC, MP3, M4A, OGG, WebM, FLAC) is now accepted.
  • "Unknown fields are silently ignored" — they are now rejected with 400. This one was actively misleading.
  • The keyterms field was documented only as word_boost.

Word timestamps need a flag

timestamps: true is accepted and returns 200, but SYNC_BFA_ALIGNMENT_ENABLED defaults to false and the aligner's init returns silently when it's off — so words come back with no start/end and 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.0 with AWS_EC2_METADATA_DISABLED=true, so instance-role credentials couldn't mask a customer-environment auth failure:

Check Result
/transcribe and /v1/transcribe Identical transcripts, both 200
No Authorization header 401
MP3 upload 200
keyterms_prompt vs word_boost Identical output
Both alias names at once 400, names the conflict
Unknown config field 400
timestamps: true, flag off 200, no start/end
timestamps: true, flag on start/end populated; aligner loads and warms
GET /warm 200 {"warm":"toasty"}
Usage reporting Reaches usage-tracker as sync_transcription_self_hosted, 200

The 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

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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant