chore(deps): bump googleapis/release-please-action from 4.4.0 to 5.0.0 - #64
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps [googleapis/release-please-action](https://github.com/googleapis/release-please-action) from 4.4.0 to 5.0.0. - [Release notes](https://github.com/googleapis/release-please-action/releases) - [Changelog](https://github.com/googleapis/release-please-action/blob/main/CHANGELOG.md) - [Commits](googleapis/release-please-action@16a9c90...45996ed) --- updated-dependencies: - dependency-name: googleapis/release-please-action dependency-version: 5.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
GregHolmes
added a commit
that referenced
this pull request
Aug 18, 2026
…twine >=7 (#95) Audit of outdated dependencies turned up a **live user-facing bug**, so this PR leads with the fix. ## 1. `dg mcp` is broken for every new install 🔴 `deepgram-mcp 0.1.1` declares an unbounded `mcp>=1.0.0`. mcp **2.0** removed `streamablehttp_client` from `mcp.client.streamable_http`, which `deepgram-mcp` still imports — so a fresh `pip install deepctl` resolves mcp 2.0.0 and: ``` $ dg mcp Error running MCP proxy: cannot import name 'streamablehttp_client' from 'mcp.client.streamable_http' ``` Reproduced in a clean venv against the **released 0.2.27 wheel** — this is not caused by this branch. **Why tests didn't catch it:** all 1052 unit tests pass, because they mock `run_proxy`. Only a live invocation fails. (Those `coroutine 'run_proxy' was never awaited` warnings in the suite are that mock.) **Fix:** cap `mcp>=1.0.0,<2.0.0` in `deepctl-cmd-mcp` until `deepgram-mcp` supports 2.x. Verified `dg mcp` returns a valid `initialize` response on mcp 1.29.0. ## 2. Nothing was pinned across environments `uv.lock` had been gitignored since the initial commit, and CI ran `uv sync --group testing` with no lock — so local, CI, the publish-action image and end users each resolved independently. That is the same class of problem behind both this mcp break and the 0.2.27 publish failure. - Commit `uv.lock` - CI now uses `uv sync --group testing --locked`, so drift shows up as a reviewable diff instead of a surprise Note this fixes **dev/CI reproducibility only** — it does not constrain end users. Upper bounds in `pyproject.toml` (item 1) are the only thing that protects them. ## 3. `twine>=7.0.0` for dev twine <7 rejects `Metadata-Version: 2.5` (emitted by hatchling) — the exact cause of the failed 0.2.27 publish. The venv had twine 6.2.0, so `make verify-packages` **would** have caught it locally, while CI's fresh `pip install twine` always got 7.x and always passed. Raising the floor keeps local verification equal to what actually publishes. ## Verification - `ruff format` / `ruff check` / `mypy` clean (on ruff **0.16.3**, up from 0.15.21) - **1052 passed**, 6 skipped - `dg mcp` initialize verified live on mcp 1.29.0 - Full **68-check live API smoke suite** passes (STT files/URLs/live-stream/mic, TTS Aura + Flux incl. `--speed`/`--expressivity`, read, account, api, mcp) - Lockfile also moves websockets 16.1 → **17.0.1**; verified Flux TTS streaming and live STT both work on it ## Deliberately not included - `astro 6 → 7` in `web/` (clears **20 npm security alerts**, 11 high) — separate PR, needs a site check - The 6 stale Dependabot PRs (#61, #64, #81–84) - No `npm` ecosystem and only `pip` at `/` in `dependabot.yml`, so `web/` and the 31 `packages/*` are never scanned — worth a follow-up
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 googleapis/release-please-action from 4.4.0 to 5.0.0.
Release notes
Sourced from googleapis/release-please-action's releases.
Changelog
Sourced from googleapis/release-please-action's changelog.
... (truncated)
Commits
45996edchore(main): release 5.0.0 (#1200)a8121b9chore: build dist (#1201)f533c26fix: bump release-please from 17.3.0 to 17.6.0 (#1199)46dfc01feat!: upgrade to node24 (#1188)5c625bfchore(main): release 4.4.1 (#1187)8bb7a2echore: build dist (#1186)ef9c274fix: bump release-please from 17.1.3 to 17.3.0 (#1183)64d83e9docs(README): add missing action inputs + package options (#1176)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)