Release status¶
Last reviewed: 2026-08-20.
VAANI 1.0.0rc43 is the current installable private release for the merged
provider-reliability work tracked by #173–#177. Its exact wheel and sdist were
uploaded once to the approved private Google Artifact Registry, read back with
matching hashes under separate authentication, and installed from that
registry in a clean Python 3.13 environment. It adds safe streamed provider
recovery, cancellation-resilient truthful closure, fatal remote SIP leg
termination, immutable birla-prod-v42@14, and source-and-sdist public
contract 7.24.0. It remains unavailable on public PyPI. Source and runtime
marker: rc43-release-state:published_private.
create-vaani-app 0.2.1rc19 is the current separately published Starter.
It was uploaded once to the same private Google Artifact Registry, read back
with separate authentication and no cache, and installed by exact version in
a fresh Python 3.13 environment. Its wheel is 849597 bytes with SHA-256
b06c20e7c1c5c906e36d33cc316ce931fa3312d9c25b8ffc10c46c15534615ed; its
sdist is 847830 bytes with SHA-256
a4a7815221230fb866cc945d7151f5f98d7629a8ee5836632c4f9c54e1a3e4b8.
The generated application pins VAANI rc43 and passed its six backend tests,
eight frontend tests, TypeScript, lint, production build, and zero-vulnerability
production audit. It remains unavailable on public PyPI. The source artifact
commit is aaebb34b271584ea001628d3f3c7eccc9535289a; that source checkout has
no configured Git remote, so no remote source provenance is claimed. The
published sdist is the immutable recovery artifact and is usable without
.git. See the Starter rc19 publication evidence.
VAANI 1.0.0rc42 is the historical installable private release for the merged
issue #168 Ozonetel caller-identity fixes. Its exact wheel and sdist were
published to the approved private Google Artifact Registry, read back with
matching hashes, and installed from that registry in a clean Python 3.13
environment. It remains unavailable on public PyPI. Source and runtime marker:
rc42-release-state:published_private.
VAANI 1.0.0rc41 is the historical installable private release for the merged
issue #164 conversation wall-clock timing publication fixes. Its exact wheel
and sdist were published to the approved private Google Artifact Registry,
read back with matching hashes, and installed from that registry in a clean
Python 3.13 environment. It remains unavailable on public PyPI. Source and
runtime marker: rc41-release-state:published_private.
The source default BIRLA_PROD_V42 resolves to the immutable
birla-prod-v42@14 preset published in rc43. Historical rc42 installs remain
paired with birla-prod-v42@13; historical rc41 installs remain paired with
birla-prod-v42@12.
VAANI 1.0.0rc40 is the previous installable private release for the merged
issue #160 live-startup admission fixes. Its exact wheel and sdist were
published to the approved private Google Artifact Registry, read back with
matching hashes, and installed from that registry in a clean Python 3.13
environment. It remains unavailable on public PyPI. Source and runtime marker:
rc40-release-state:published_private.
Historical release marker: rc39-release-state:published_private.
VAANI 1.0.0rc39 was the previous installable private release. It adds the
immutable birla-prod-v42@12 BEST_EFFORT recording preset and the documented
deployment-owned transfer/persona routing patterns. Its exact wheel and sdist
were published to the approved private Google Artifact Registry, read back
with matching hashes, and installed from that registry in a clean Python 3.13
environment. It remains unavailable on public PyPI. Source and runtime marker:
rc39-release-state:published_private.
Historical release marker: rc38-release-state:published_private.
Historical release marker: rc37-release-state:published_private.
Historical Starter create-vaani-app 0.2.1rc18 remains available for
reproduction; its generated projects pin its audited rc36 runtime bytes.
vaani-evals 0.1.1
accepts >=1.0.0rc32,<2.0.0.dev0, so future compatible Vaani 1.x releases
work without an eval-package release; every 2.x development, prerelease, and
stable build is rejected as breaking.
rc32 passed its deterministic clean-wheel gate, authenticated registry publication and clean install, and one credentialed synthetic LiveKit text attempt. The attempt used deterministic providers and a sandbox tool; it did not use production customer data, business APIs, or production side effects. See Release and prove the evaluation contract and the machine-readable operational evidence.
Historical release marker: rc36-release-state:published_private.
Current rc43 private release¶
The rc43 release contains the merged #173–#177 implementation built from source
commit 565d5ce5e0243214eab0cdfac2f1be7029df339c. Deterministic tests cover provider recovery and
privacy-safe correlated warnings, LiveKit shutdown completion, remote SIP leg
termination and transfer preservation, Birla preset @14, and public contract
7.24.0. The
clean preparation commit produced a 293688-byte wheel with SHA-256
5d91a59011010702cfa14321b02b60d7499700321753d4396f6f35b5caf2057b
and a 556908-byte sdist with SHA-256
077dfb0468b3966353c7302267672a1debc63b556ca36abd937636874486d396.
The canonical double build, 278-entry privacy scan, twine check, local Python
3.13 wheel install, source-and-sdist contract 7.24.0 verification, docs, strict
MkDocs, compileall, and 263 focused tests passed. The installed wheel separately
verified version, the birla-prod-v42@14 preset, termination seam, and scripted
call provenance; the public contract manifest and lock are not packaged in the
wheel. A single collision-failing private upload succeeded, and separately
authenticated no-cache read-back matched both exact hashes. A clean Python
3.13.11 private-index install had no editable or local-path provenance and no
direct_url.json; it verified rc43, preset @14, privacy-safe provider
correlation and recovery, cancellation-to-shutdown completion exactly once,
the SIP termination seam, and a completed scripted call. Credentialed
Vertex/LiveKit/GCS/Ozonetel validation, a production canary, a consumer repin,
and rollout approval remain unclaimed. See the
rc43 preparation evidence.
Historical rc42 private release¶
The rc42 release is the merged issue #168 implementation from source commit
44625205226a7e4c0b6f3b5fe5445360a873c94a. The clean-commit wheel is 283724
bytes with
SHA-256 3facd46530192ee18b45c4647cfd6ce96bf67aa1bb35861c941ee981b24b441c,
and the sdist is 546113 bytes with SHA-256
dcc277e4d39a604f4138304eafa92cdf6dced03d2fa78c08a278a8bc77f8da95.
The canonical two-snapshot build and 276-entry privacy scan passed, as did
twine check, contracts, docs, strict MkDocs, and compileall. Authenticated
registry read-back matched both exact hashes. A fresh Python 3.13.11 registry
install used the approved provider extras, had no direct_url.json, reported
version 1.0.0rc42, loaded birla-prod-v42@13 with digest
f51be287ed60cabf1a65769e38818ed7cc00a5473d8be2a683b821927dfc4135, and
passed all 10 installed issue #168 public alias tests. Credentialed LiveKit,
GCS, SIP, Salesforce, and SMS validation remain outside this record. See the
rc42 preparation evidence.
Historical rc41 private release¶
The rc41 artifacts were published from source and merge commit
e2432c5ce8280e6d351f69d6c27fa5026280952d to the approved private registry.
The exact upload wall-clock timestamp was not captured. The wheel
vaani-1.0.0rc41-py3-none-any.whl is 281300 bytes with SHA-256
eb98370de9256ad317b565b3f0e8e10e7b4a4ace749ff87112e33482269d2623; the
sdist vaani-1.0.0rc41.tar.gz is 544363 bytes with SHA-256
795268c51c66353f9fb0028a14b9427d1b077b030f774900b91a38fabaeda4a9.
Authenticated private-registry read-back matched both exact hashes. A clean,
non-editable, non-local Python 3.13.11 registry install imported from
site-packages, had no direct_url.json, and reported version 1.0.0rc41.
The four issue #164 wall-clock timing publication tests passed against the
installed artifact.
The companion rc41 publication evidence
records the published artifact identities, read-back state, source revision,
and public contract version 7.22.0. Credentialed GCS recording,
Ozonetel/Salesforce screen-pop, and real LiveKit/SIP DID routing were not
run; this publication record does not certify those operational gates.
Historical rc40 private release¶
The rc40 artifacts were published on 2026-08-17 from source
850df8ccf7518cbcd25f167194c06dc4dbdead92 after merge commit
cc6019fc9bbaef1222053eb30e311f9994eaf233 to the approved private registry.
The exact upload wall-clock timestamp was not captured.
The wheel vaani-1.0.0rc40-py3-none-any.whl is 280858 bytes with SHA-256
00747ca0d7f970ba9fbcd2f140fee9c158f901e299e2c08066450a2bb435ed82; the
sdist vaani-1.0.0rc40.tar.gz is 543266 bytes with SHA-256
88442344426fe1bb3c49da19643014a0073862a552ebbbf2ecf403e94c5ccc42.
Authenticated private-registry read-back matched both exact hashes. A clean,
non-editable, non-local Python 3.13 registry install imported from
site-packages, had no direct_url.json, reported version 1.0.0rc40, and
loaded birla-prod-v42@12 with BEST_EFFORT recording and its
recording-gcs extra. The issue #160 registry readiness shard passed 11 tests,
including admission-before-assistant execution and post-startup definition
freezing.
The deterministic build used two separate clean snapshots and produced byte-identical wheel and sdist archives. The 274-entry archive privacy scan, contract verification, documentation checks, and focused release tests passed. Credentialed GCS recording, Ozonetel/Salesforce screen-pop, and real LiveKit/SIP DID routing were not run; this publication record does not certify those operational gates.
The companion rc40 publication evidence
records the published artifact identities, read-back state, source revision,
and public contract version 7.22.0.
Historical rc39 private release¶
The rc39 artifacts were published at 2026-08-17T14:34:18Z from source
a19619e43be96b15b5951a32d044f50a21911f25 to the approved private registry.
The wheel vaani-1.0.0rc39-py3-none-any.whl is 278501 bytes with SHA-256
b85f458bf0ba016036580895f4b37262a570da47928df17b127ba926e27c8be3; the
sdist vaani-1.0.0rc39.tar.gz is 539897 bytes with SHA-256
0a5982b139eb21e651708edc4c92b6305387df70091ed6a506bf456d2efcfe31.
Authenticated Artifact Registry read-back matched both exact hashes. A clean,
non-editable, non-local Python 3.13 registry install imported from
site-packages, had no direct_url.json, reported version 1.0.0rc39, and
loaded birla-prod-v42@12 with BEST_EFFORT, recording-gcs, and rhea.
The deterministic build used two separate clean snapshots and produced byte-identical wheel and sdist archives. The 274-entry archive privacy scan, contract verification, documentation checks, strict MkDocs in definitive review, and the issue's focused deterministic gates passed. Credentialed GCS recording, Ozonetel/Salesforce screen-pop, and real LiveKit/SIP DID routing were not run; this publication record does not certify those operational gates.
The companion rc39 publication evidence
records the published artifact identities, read-back state, source revision,
and public contract version 7.22.0.
Historical rc38 private release¶
The rc38 artifacts were published at 2026-08-17T04:54:10Z from source
6bb9ec12e6c6324f25c3f6ca6026533079ccca63 to the approved private registry.
The wheel vaani-1.0.0rc38-py3-none-any.whl is 277063 bytes with SHA-256
20e257d0a869fb6c4077456466c12fc8b0998b8ef8bcb4f62e00c0cb67cdd1e3; the
sdist vaani-1.0.0rc38.tar.gz is 537755 bytes with SHA-256
f66a65acfd66d0bef1028189359b55cb805ee4cf30a725614acf94e0385d214e.
Authenticated Artifact Registry read-back matched both exact hashes. A clean,
non-editable, non-local Python 3.13 registry install imported from
site-packages, had no direct_url.json, and reported version 1.0.0rc38.
The installed wheel includes birla-prod-v42@11, its rhea voice, and the
allowlisted ucid, mucid, did, and callerno metadata keys.
The focused release checks passed 73 tests, and the contract/status shard passed 36 tests. Contract verification, documentation checks, deterministic double build, and the 272-entry archive privacy scan passed. Credentialed SmallestAI Rhea audio and consumer-owned LiveKit/SIP routing were not run; this publication record does not certify those operational gates.
The companion rc38 publication evidence
records the published artifact identities, read-back state, source revision,
and public contract version 7.22.0.
Historical rc37 private release¶
The rc37 artifacts were published at 2026-08-13T22:24:03Z from source
3ac5eb004afeb5081d668bb6c1a7437f4532797b to the approved private registry.
The wheel vaani-1.0.0rc37-py3-none-any.whl is 274955 bytes with SHA-256
cf6ffc9c2363d5e10730ed2f754c94162444bfd8bccb51025ce37c569c3172e5; the
sdist vaani-1.0.0rc37.tar.gz is 533572 bytes with SHA-256
f4d81d31172a689e499e3416e0197053db7052f30e8a2c5edbd2712e945e6c43.
Authenticated Artifact Registry read-back matched both exact hashes. A clean,
non-editable, non-local Python 3.13 registry install imported from
site-packages, had no direct_url.json, reported version 1.0.0rc37, and
passed all five public API probes.
Repository source validation is recorded as 942 tests passed and 65
declared skips. The initial full run passed 940; its only two failures were
docs-site tests hard-coded to unavailable local .venv executable paths.
Re-running that nine-test docs-site file with the expected executable path
passed all nine, so the aggregate reports the harness rerun rather than a
runtime defect. Contracts, documentation checks, strict MkDocs, compileall,
twine check, deterministic double build, and the 270-entry archive privacy
scan passed. Hosted credentialed LiveKit metadata propagation was not run;
the registry and deterministic public-probe evidence does not certify that
operational gate.
The companion release gate consumes the strict
rc37 publication evidence, which records
only the published artifact identities, read-back state, source revision, and
public contract version 7.19.0.
Historical rc36 consolidated release¶
The rc36 local wheel and sdist were built twice from separate clean snapshots
of one committed source tree. Commit-epoch normalization produced byte-identical
wheel and sdist archives, and both source snapshots remained clean. The archive
privacy gate rejected unsafe members, operational evidence, identifiers,
secrets, customer contact data, bucket and recording URLs, and vendor/build
directories; historical operational evidence is not packaged. Two clean
non-editable installations of the exact wheel executed the public Assistant
path: an ASSISTANT_PREPARATION terminal result bypassed conversation, a
mid-call terminal played media and fenced the follow-up, bounded response-watch
recovery played out, tool-bearing preparation declared but did not invoke its
tool, and an enabled immutable approved recording adapter preserved its artifact
and binding while the disabled negative was rejected before ownership.
The exact commands, publication, read-back hashes, and registry-install probes
are recorded in the
rc36 publication evidence.
The full tests/ run passed 896 tests and skipped 65 declared
credential-dependent tests. Contract verification, documentation checks,
strict MkDocs, compileall, twine check, archive-content validation, and two
fresh non-editable wheel probes also passed.
The required clean release gate is the full repository test suite,
python contracts/verify.py, python scripts/check_docs.py, strict MkDocs,
compileall, the canonical deterministic double build, twine check, the
archive privacy/content gate, and two fresh non-editable wheel installations
running both public-API probes.
The exact wheel and sdist were uploaded to the approved private registry and downloaded again without cache; both read-back hashes match. A fresh Python 3.13 registry install had no editable or local-path provenance and passed all five public probes. Credentialed LiveKit and GCS validation has not run. SIP, Salesforce, and SMS validation remains consumer-owned and has not run.
Private releases¶
VAANI 1.0.0rc43 is the current private runtime in Google Artifact Registry.
create-vaani-app 0.2.1rc19 is the current separately published Starter and
locks generated backends to VAANI rc43. vaani-evals 0.1.1 is also published
privately and supports compatible Vaani 1.x versions.
| Package | Source | Wheel SHA-256 | sdist SHA-256 |
|---|---|---|---|
vaani==1.0.0rc43 |
565d5ce5e0243214eab0cdfac2f1be7029df339c |
5d91a59011010702cfa14321b02b60d7499700321753d4396f6f35b5caf2057b |
077dfb0468b3966353c7302267672a1debc63b556ca36abd937636874486d396 |
vaani==1.0.0rc42 |
44625205226a7e4c0b6f3b5fe5445360a873c94a |
3facd46530192ee18b45c4647cfd6ce96bf67aa1bb35861c941ee981b24b441c |
dcc277e4d39a604f4138304eafa92cdf6dced03d2fa78c08a278a8bc77f8da95 |
vaani==1.0.0rc41 |
e2432c5ce8280e6d351f69d6c27fa5026280952d |
eb98370de9256ad317b565b3f0e8e10e7b4a4ace749ff87112e33482269d2623 |
795268c51c66353f9fb0028a14b9427d1b077b030f774900b91a38fabaeda4a9 |
vaani==1.0.0rc40 |
850df8ccf7518cbcd25f167194c06dc4dbdead92 |
00747ca0d7f970ba9fbcd2f140fee9c158f901e299e2c08066450a2bb435ed82 |
88442344426fe1bb3c49da19643014a0073862a552ebbbf2ecf403e94c5ccc42 |
vaani==1.0.0rc39 |
a19619e43be96b15b5951a32d044f50a21911f25 |
b85f458bf0ba016036580895f4b37262a570da47928df17b127ba926e27c8be3 |
0a5982b139eb21e651708edc4c92b6305387df70091ed6a506bf456d2efcfe31 |
vaani==1.0.0rc38 |
6bb9ec12e6c6324f25c3f6ca6026533079ccca63 |
20e257d0a869fb6c4077456466c12fc8b0998b8ef8bcb4f62e00c0cb67cdd1e3 |
f66a65acfd66d0bef1028189359b55cb805ee4cf30a725614acf94e0385d214e |
vaani==1.0.0rc37 |
3ac5eb004afeb5081d668bb6c1a7437f4532797b |
cf6ffc9c2363d5e10730ed2f754c94162444bfd8bccb51025ce37c569c3172e5 |
f4d81d31172a689e499e3416e0197053db7052f30e8a2c5edbd2712e945e6c43 |
vaani==1.0.0rc36 |
072de7f5cc9b80f3e0e842f1e0cb2d2be6e31472 |
6948a3a34a447e244a07514331da4835caa7e7a4b9938f369fa1da62f801eb2d |
639c0b5c255e854ccf08faecba6e7444862994dc60aec258acc7fc73c4d1ad51 |
vaani==1.0.0rc35 |
0286433aa251bd09310a0d12e679cd6a29c47676 |
56094dcc78be46c97289e5d210747e7f8f820625317cc3c938537a4b6b9ee205 |
6c6503af81ee50c77a51b524883b7262114fcd6279d4f90a48fa72a87c0d19e8 |
vaani==1.0.0rc34 |
c62fff74fdaddc3d53de6890f74ae4c575cf32c5 |
56ae74c1e9aeca7715c3255b4503836561f0c515df4ecbf9d04f7dbbfa9da08b |
fe0b289ff70c31cbb450f8176e09e560b0dad4686a1aea5cb58e1cb8b7676408 |
vaani==1.0.0rc32 |
f2c7d332db69ae35fdf06fb6f0b30deecccfe4a0 |
4032adc3d645815f9af44582f745c79c6c76af462aa101cc7f71dd7f0eb8b741 |
cb846f96a86402b89a18de927ba186ad3805633dd126dd8e02aa6b419ceb6d10 |
vaani==1.0.0rc31 |
d2134ec49443e334c2fc89008c89699122d7adde |
3e063d02d73957ee384362fe827b556945a7d8fc68871d2dc5c2f049088c701c |
5d6eb8445d76665d64155430529a74fbc3c9103e36bfdd4819f8ea1403585470 |
create-vaani-app==0.2.1rc19 |
aaebb34b271584ea001628d3f3c7eccc9535289a |
b06c20e7c1c5c906e36d33cc316ce931fa3312d9c25b8ffc10c46c15534615ed |
a4a7815221230fb866cc945d7151f5f98d7629a8ee5836632c4f9c54e1a3e4b8 |
create-vaani-app 0.2.1rc18 (historical) |
2901d51653e5617ae022d91ecf0bf54b7c78d38e |
19d9d7886277f48ffea5a4bd717130463046ca3d2f6595b0ad8007ca841bfb47 |
8a3696879e64136ed48fa1399a486edcf8a7f1de1c5e2205dacb80fb5563e9e8 |
vaani-evals==0.1.1 |
0c0fb78d6418b34702930181741d4ba63380efce |
0381a6841e5382a01800cbc923887aed164e13ea45d2f7acfadcf655c09387dd |
c87dc5a3a1dcf36ff8cbabebe2b704f6fd4660146e7ef73fb0a1cc1110463bc2 |
An authenticated clean environment running Python 3.13 installed rc31 from that
registry with the Deepgram, Google, and SmallestAI extras and verified
vaani.__version__ == "1.0.0rc31" from its isolated virtual
environment. Fresh registry downloads matched both recorded archive hashes.
See the machine-readable publication record.
That historical rc31 installation proof did not place a credentialed provider
call, join a LiveKit room, or place a SIP call.
For rc36, authenticated downloads matched both uploaded archive hashes and a new Python 3.13 environment installed the exact private-index artifact without editable or local-path provenance. All five public release probes passed. Credentialed provider and consumer-owned integration gates remain explicitly out of scope for this release record.
For rc37, authenticated Artifact Registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact
private-index artifact without editable or local-path provenance, imported it
from site-packages with no direct_url.json, and passed all five public release
probes. Hosted credentialed LiveKit metadata propagation has not run.
For rc38, authenticated Artifact Registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact private-index
artifact without editable or local-path provenance and found no
direct_url.json. The installed package identity and Birla preset surface were
verified; credentialed Rhea audio and consumer-owned LiveKit/SIP routing were
not run.
For rc43, authenticated private-registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact no-cache
private-index wheel without editable or local-path provenance, found no
direct_url.json, and verified version 1.0.0rc43, the @14 Birla preset,
privacy-safe provider recovery/correlation, cancellation-safe completion, the
SIP termination seam, and a scripted call. Credentialed provider, LiveKit,
GCS, Ozonetel, and real SIP gates remain unclaimed.
For rc42, authenticated private-registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact
private-index artifact without editable or local-path provenance, found no
direct_url.json, and verified version 1.0.0rc42, the @13 Birla preset
digest, and all 10 issue #168 public alias tests. Credentialed GCS,
Ozonetel/Salesforce, and real SIP/DID routing remain consumer-owned gates.
For rc40, authenticated private-registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact
private-index artifact without editable or local-path provenance, found no
direct_url.json, and verified version 1.0.0rc40, the @12 BEST_EFFORT
recording identity, and the issue #160 registry readiness behavior. Credentialed
GCS, Ozonetel/Salesforce, and real SIP/DID routing remain consumer-owned gates.
For rc39, authenticated Artifact Registry read-back matched both uploaded
archive hashes. A new Python 3.13 environment installed the exact private-index
artifact without editable or local-path provenance, found no direct_url.json,
and verified the @12 BEST_EFFORT recording identity. Credentialed GCS,
Ozonetel/Salesforce, and real SIP/DID routing remain consumer-owned gates.
For rc32, authenticated downloads matched both uploaded archive hashes and a
new Python 3.13 environment installed the exact private-index artifact without
editable or local-path provenance. A disposable rc32 worker then registered in
LiveKit India South and completed the identity-bound text attempt
issue-110-rc32-livekit-attempt-1. Its finalized result includes participant
and agent transcript items, the returned sandbox lookup_ticket tool, a
CLOSED lifecycle, timing and usage ledgers, and the honest
NOT_CONFIGURED Judge status. Providers were deterministic fakes; the room,
dispatch, text streams, control stream, and evidence packets used the hosted
LiveKit service.
An authenticated, no-cache uvx run installed Starter rc19 from GAR and
generated a fresh project. Its setup installed VAANI rc43 from GAR; the
generated backend passed 6 tests, and the frontend passed 8 tests, TypeScript,
ESLint, its production build, and npm audit --omit=dev with zero
vulnerabilities. The source archive has no Git remote provenance; its supported
recovery path verifies the embedded manifest before rebuilding without .git.
See the Starter rc19 publication evidence.
The previous Starter rc18 publication remains historical: its setup installed VAANI rc36, and its exact hashes remain recorded below for reproduction.
The Loyalty consumer at
fd0e5cca71c917ca4bcb1716473de16e9a7dca0b then locked and installed those
same GAR hashes without an editable or local-path VAANI install. Its full gate
passed 319 backend tests, 14 frontend tests, Prettier, ESLint, TypeScript, the
Next.js production build, and both development and production configuration
checks. This remains deterministic/configuration acceptance, not a
credentialed human-audio UAT claim.
Published rc32 source verification¶
The rc32 release tree was verified at
f2c7d332db69ae35fdf06fb6f0b30deecccfe4a0. From a clean worktree, bounded
commands produced these results:
- the final full
tests/run passed831tests with65credential-dependent skips; - the evaluation, contract, transport, lifecycle, and release-focused shard
passed
71tests with all declared provider extras installed; python contracts/verify.pyreportedVAANI v1 contracts verified;python scripts/check_docs.pyvalidated all 32 Markdown files and compiled source examples;- strict MkDocs, compileall, and the rc32 operational evidence validator passed;
- two builds produced identical wheel bytes. The uploaded wheel and sdist both
passed
twine check; authenticated downloads matched the recorded hashes.
VAANI does not configure separate lint or static-type-checker commands, so no
lint/type pass is claimed for this source tree. Contract verification is its
configuration gate. The stable, HR, fleet, gate-runner, and voice-console
wrapper tests intentionally execute their immutable historical source
revisions; those results certify the named historical artifacts, not current
HEAD implementations. Current stable tooling and console fail-closed behavior
also have small direct smoke tests in test_current_tree_release_tooling.py.
Package paths include:
.../vaani-python/vaani/vaani-1.0.0rc43-*.../vaani-python/vaani/vaani-1.0.0rc42-*.../vaani-python/vaani/vaani-1.0.0rc41-*.../vaani-python/vaani/vaani-1.0.0rc40-*.../vaani-python/vaani/vaani-1.0.0rc39-*.../vaani-python/vaani/vaani-1.0.0rc38-*.../vaani-python/vaani/vaani-1.0.0rc36-*.../vaani-python/vaani/vaani-1.0.0rc37-*.../vaani-python/vaani/vaani-1.0.0rc35-*.../vaani-python/vaani/vaani-1.0.0rc32-*.../vaani-python/vaani/vaani-1.0.0rc31-*.../vaani-python/create-vaani-app/create_vaani_app-0.2.1rc19-*.../vaani-python/create-vaani-app/create_vaani_app-0.2.1rc18-*(historical).../vaani-python/vaani-evals/vaani_evals-0.1.1-*
Consumer evidence¶
The rc27 loyalty consumer remains the latest recorded deterministic evidence
for one real
Assistant.run using scripted adapters and a local fake logging HTTP service.
The call completed with a successful Judge report and consumer evidence, then
its completion handler emitted exactly one logging request. This is
credential-free fake-service evidence, not a LiveKit, provider, UAT, SIP, or
human-audio acceptance claim.
The previous rc23 and rc26 connected runs are historical evidence only. No historical or mocked run certifies rc36, rc37, rc38, or rc39. The current rc43 record is scoped to registry identity and deterministic package-surface probes for #173–#177; each consumer must still validate its applicable business integrations, capacity, monitoring, and rollback.
Distribution¶
The private registry is:
The public PyPI project named vaani is unrelated. VAANI and the Starter are
not published to public PyPI.
Teams need read-only roles/artifactregistry.reader access and Google
authentication. Follow Installation and
then Quickstart.
Publication evidence¶
- Starter rc19 publication and recovery evidence
- rc43 publication and release gates
- rc42 publication and release gates
- rc41 publication and release gates
- rc40 publication and release gates
- rc39 publication and release gates
- rc38 publication and release gates
- rc37 publication and release gates
- rc36 publication and release gates
- rc35 publication and release gates
- rc34 historical publication and release gates
- rc32 evaluation release
- rc31 publication
- rc30 publication
- rc29 publication
- rc27 publication
- rc20 publication
- rc20 clean install
- rc20 browser-room proof
- rc19 publication
- rc19 clean install
- rc19 browser-room proof
Machine-readable facts: release-status.json.