Skip to content

whisper-cpp: bump REF to QVAC-18991 upstream-sync HEAD (validation only)#154

Closed
Zbig9000 wants to merge 1 commit into
tetherto:mainfrom
Zbig9000:QVAC-18991-validate-upstream-sync
Closed

whisper-cpp: bump REF to QVAC-18991 upstream-sync HEAD (validation only)#154
Zbig9000 wants to merge 1 commit into
tetherto:mainfrom
Zbig9000:QVAC-18991-validate-upstream-sync

Conversation

@Zbig9000

Copy link
Copy Markdown
Contributor

Summary

Validation-only PR. Single-purpose port-version bump so tetherto/qvac#TBD (QVAC-18991 validation bump of transcription-whispercpp) can run the addon CI against the QVAC-18991 upstream-sync content in isolation — no QVAC-18300 / 18992 / 18993 changes mixed in.

REF tetherto/v1.8.4.2Zbig9000/47784b9e (whisper-cpp PR #25 HEAD)
version 1.8.4.2#11.8.4.3#0
Other changes None — feature list / Android config / patches unchanged

Tasks

  • QVAC-18991 — pull latest whisper.cpp from upstream. This PR exists to give the upstream-sync content a CI surface via the qvac monorepo's transcription-whispercpp on-PR workflow.

What this validates

Once the qvac-side validation PR (TBD link) is opened and the verified label is applied, its On PR Trigger (Whispercpp) workflow will exercise:

  • sanity-checks — C++ static analysis on the rebuilt whisper-cpp source
  • cpp-tests-coverage — the addon's native test suite linked against whisper-cpp 1.8.4.3#0
  • cpp-lint
  • run-integration-tests + run-mobile-integration-tests — end-to-end addon tests
  • prebuild — the cross-platform prebuild matrix

If those go green, whisper-cpp PR #25 is proven safe to merge into tetherto/master — and after that lands + v1.8.4.3 is tagged, this PR can simply be closed (the production port version chain will arrive via vcpkg PR #152).

Notes for reviewer

Cross-repo PR set

  • whisper-cpp PR #25 — QVAC-18991 upstream sync (the thing being validated).
  • whisper-cpp PR #27 — QVAC-18966 tts-cpp <atomic> fix (independent atomic fix, can merge in parallel).
  • whisper-cpp PR #28 — QVAC-18993 bundled-ggml Android dynamic backend (the "rest" group, defer).
  • ggml-speech PR #13 — QVAC-18992 (defer).
  • vcpkg PR #152 — production speech-stack + Android dynamic backends (defer).
  • qvac PR #2124 — production transcription-whispercpp 0.7.3 (defer).
  • This PR — QVAC-18991 validation port, paired with qvac PR #TBD.

Made with Cursor

Bumps the whisper-cpp port to consume the QVAC-18991 upstream-sync
commit on the Zbig9000 fork (https://github.com/tetherto/qvac-ext-lib-
whisper.cpp/pull/25), so the transcription-whispercpp on-PR workflow
in qvac monorepo can run against the upstream-sync content in
isolation (no QVAC-18300 / 18992 / 18993 changes mixed in).

Single-purpose validation port:
  - REF: tetherto v1.8.4.2 -> Zbig9000 47784b9e (PR tetherto#25 HEAD)
  - SHA512 recomputed from the GitHub tarball
  - HEAD_REF -> QVAC-18991-pull-latest-whisper-cpp-upstream
  - version: 1.8.4.2#1 -> 1.8.4.3#0
  - No feature changes, no patches, no Android-side configuration
    changes -- the port is identical in shape to 1.8.4.2#1 except
    for the source version.

This PR is NOT meant to merge to main long-term; it exists to feed
a CI run on tetherto/qvac#TBD (QVAC-18991 validation bump of
transcription-whispercpp). After CI proves the upstream-sync source
is buildable + addon CI is green, this PR is closeable. Production
consumption of 1.8.4.3 will go through whisper-cpp PR tetherto#28 + tetherto#27 +
this port's regular tetherto#1, tetherto#2, ... port-version chain landing via
qvac-registry-vcpkg PR tetherto#152.

Refs QVAC-18991 (Asana).

Co-authored-by: Cursor <cursoragent@cursor.com>
@Zbig9000 Zbig9000 force-pushed the QVAC-18991-validate-upstream-sync branch from f844a5c to 56f1586 Compare May 20, 2026 08:30
@GustavoA1604

Copy link
Copy Markdown
Contributor

PR only used for validation of pulling from upstream in whisper-cpp. No need to merge it

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.

2 participants