chore(deps): bump astro from 6.1.6 to 6.1.10 in /web in the npm_and_yarn group across 1 directory - #81
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps the npm_and_yarn group with 1 update in the /web directory: [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Updates `astro` from 6.1.6 to 6.1.10 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@6.1.10/packages/astro) --- updated-dependencies: - dependency-name: astro dependency-version: 6.1.10 dependency-type: direct:production dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
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
Contributor
|
Closing — this is now a downgrade rather than a bump. #96 moved Dependabot will open a fresh PR against the 7.x line if a security bump is needed there. |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/web/npm_and_yarn-590454f44f
branch
August 18, 2026 15:46
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.
Bumps the npm_and_yarn group with 1 update in the /web directory: astro.
Updates
astrofrom 6.1.6 to 6.1.10Release notes
Sourced from astro's releases.
... (truncated)
Changelog
Sourced from astro's changelog.
... (truncated)
Commits
c1f2e4f[ci] release (#16467)345fb9echore: fix flaky dev toolbar render time test (#16500)5120ecd[ci] format3d82220Add AEAD context binding to server island encryption (#16457)1bcb43bPrebundle dev toolbar entrypoint in client environment (#16480)93101cc[ci] format152700efix: strip sourceMappingURL from dev toolbar entrypoint during dep optimizati...bc83041refactor(astro): migrate test utils to typescript (#16492)5c543c5refactor(astro): add internal entry points for test (#16473)1058428Suppress content config warning for projects without content collections (#16...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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.