chore(release): bump version to 0.19.0 across all sources#358
Merged
Conversation
Bumps all version sources to 0.19.0 (workspace Cargo.toml + cli minutes-core dep, tauri.conf.json, mcp + sdk package.json/package-lock, manifest.json, manifest.mcpb.json, MCP_SERVER_VERSION in index.ts) and regenerates derived files (Cargo.lock, site/lib/release.ts, llms.txt + llms-full.txt, generated agent-doc date stamps). The mcp -> minutes-sdk dependency intentionally stays ^0.18.0 here: bumping it to ^0.19.0 would break npm install in CI before sdk 0.19.0 is published. It is bumped during the publish sequence (after sdk 0.19.0 is on npm) so the published mcp 0.19.0 carries the sensitivity enforcement from the republished sdk. 0.19.0 highlights: opt-in sherpa SOTA engine, agent-layer sensitivity enforcement, per-sensitivity audio retention, CI gate + macOS cache fix. whisper-guard is unchanged since v0.18.14 (no independent publish needed).
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
Summary
Version bump to 0.19.0 across all sources, per the release checklist. This is the release that ships this cycle's work: the opt-in sherpa SOTA engine, agent-layer sensitivity enforcement, per-sensitivity audio retention, the CI gate, and the macOS cache fix.
Minor bump (0.18.14 -> 0.19.0): new opt-in engine + new consent features, fully backward-compatible. No config changes required to upgrade; whisper stays the default for every existing install.
Version sources bumped (all to 0.19.0)
Cargo.toml(workspace) and theminutes-coredep version incrates/cli/Cargo.tomltauri/src-tauri/tauri.conf.jsoncrates/sdk/package.json+package-lock.json(vianpm version)crates/mcp/package.json+package-lock.json(vianpm version)manifest.jsonandmanifest.mcpb.json(kept equal, per the MCPB bundle guard)MCP_SERVER_VERSIONincrates/mcp/src/index.tsRegenerated derived files:
Cargo.lock,site/lib/release.ts,site/public/llms.txt+llms-full.txt, and the generated agent-doc date stamps.Intentional: mcp -> minutes-sdk stays
^0.18.0in this PRBumping it to
^0.19.0now would breaknpm installin the MCP CI job, because sdk 0.19.0 is not published yet. It is bumped during the publish sequence (afternpm publishof sdk 0.19.0), so the published mcp 0.19.0 depends on the new sdk and carries the sensitivity enforcement from #350. Documented in the handoff.whisper-guard
Unchanged since v0.18.14, so it does not need an independent crates.io publish this cycle (stays 0.3.0).
Verification
Cargo.lockminutes-core at 0.19.0.cargo check --workspace --no-default-featuresclean.sync_site_release_version.mjs --checkandgenerate_llms_txt.mjs --checkboth pass.