Skip to content

chore(deps): bump @ai-sdk/azure from 3.0.95 to 4.0.26 - #1576

Open
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/ai-sdk/azure-4.0.26
Open

chore(deps): bump @ai-sdk/azure from 3.0.95 to 4.0.26#1576
dependabot[bot] wants to merge 1 commit into
devfrom
dependabot/npm_and_yarn/dev/ai-sdk/azure-4.0.26

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 3, 2026

Copy link
Copy Markdown
Contributor

Bumps @ai-sdk/azure from 3.0.95 to 4.0.26.

Release notes

Sourced from @​ai-sdk/azure's releases.

@​ai-sdk/xai@​4.0.25

Patch Changes

  • 93b2acd: chore: centralize response metadata conversion
  • Updated dependencies [5fc7da5]
  • Updated dependencies [93b2acd]
    • @​ai-sdk/provider-utils@​5.0.18
    • @​ai-sdk/openai-compatible@​3.0.20

@​ai-sdk/xai@​4.0.24

Patch Changes

  • Updated dependencies [fa95504]
    • @​ai-sdk/provider-utils@​5.0.17
    • @​ai-sdk/openai-compatible@​3.0.19

@​ai-sdk/react@​3.0.242

Patch Changes

  • ai@6.0.240

@​ai-sdk/vue@​3.0.240

Patch Changes

  • ai@6.0.240

@​ai-sdk/vue@​3.0.239

Patch Changes

  • ai@6.0.239

@​ai-sdk/svelte@​3.0.225

Patch Changes

  • ai@5.0.225

@​ai-sdk/svelte@​3.0.224

Patch Changes

  • ai@5.0.224

@​ai-sdk/gateway@​3.0.162

Patch Changes

  • b28367e: feat(provider/gateway): add has provider option for model capability filtering, supporting 'implicit-caching' and 'vision' (image input)
Changelog

Sourced from @​ai-sdk/azure's changelog.

4.0.26

Patch Changes

  • Updated dependencies [d8210b6]
  • Updated dependencies [beaecb3]
  • Updated dependencies [b192878]
    • @​ai-sdk/provider-utils@​5.0.16
    • @​ai-sdk/openai@​4.0.25
    • @​ai-sdk/deepseek@​3.0.17

4.0.25

Patch Changes

  • Updated dependencies [1659cd5]
  • Updated dependencies [6a5bdff]
    • @​ai-sdk/provider-utils@​5.0.15
    • @​ai-sdk/deepseek@​3.0.16
    • @​ai-sdk/openai@​4.0.24

4.0.24

Patch Changes

  • 96a237d: Add blocked domain filters to the OpenAI and Azure Responses API web search tools.
  • Updated dependencies [96a237d]
    • @​ai-sdk/openai@​4.0.23

4.0.23

Patch Changes

  • Updated dependencies [0c464d9]
  • Updated dependencies [c49380c]
    • @​ai-sdk/provider-utils@​5.0.14
    • @​ai-sdk/openai@​4.0.22
    • @​ai-sdk/deepseek@​3.0.15

4.0.22

Patch Changes

  • Updated dependencies [1e2f324]
    • @​ai-sdk/provider@​4.0.4
    • @​ai-sdk/deepseek@​3.0.14
    • @​ai-sdk/openai@​4.0.21
    • @​ai-sdk/provider-utils@​5.0.13

4.0.21

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [@ai-sdk/azure](https://github.com/vercel/ai/tree/HEAD/packages/azure) from 3.0.95 to 4.0.26.
- [Release notes](https://github.com/vercel/ai/releases)
- [Changelog](https://github.com/vercel/ai/blob/main/packages/azure/CHANGELOG.md)
- [Commits](https://github.com/vercel/ai/commits/@ai-sdk/azure@4.0.26/packages/azure)

---
updated-dependencies:
- dependency-name: "@ai-sdk/azure"
  dependency-version: 4.0.26
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Aug 3, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d52e2add06

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread package.json
"dependencies": {
"@ai-sdk/amazon-bedrock": "~4.0.120",
"@ai-sdk/azure": "~3.0.77",
"@ai-sdk/azure": "~4.0.26",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Commit the matching bun.lock update

This dependency bump only changes package.json, but the root bun.lock still pins @ai-sdk/azure to ~3.0.77 / 3.0.77. I checked .github/workflows/ci.yml and Dockerfile, and the app install/build paths run bun install --frozen-lockfile, so CI and production image builds will not have a committed lockfile entry for ~4.0.26 and can fail or continue using the stale resolved dependency instead of the intended upgrade. Please regenerate and commit the root lockfile with this bump.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Confirmed — this is the correct diagnosis and it is the sole cause of the four red checks. All four failing jobs (Test, Lint, and Type Check, Validate CDK Infrastructure, Auth Edge Production Artifact, Unified Content PostgreSQL Lifecycle) die at the install step with:

error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile

bun.lock still has "@ai-sdk/azure": "~3.0.77" (line 8) and @ai-sdk/azure@3.0.77 (line 230), while package.json now asks for ~4.0.26.

I could not apply the fix: regenerating the lockfile requires bun install, and this routine's sandbox has no egress to registry.npmjs.org (403 on every request). See the PR-level comment for the systemic finding and the AI SDK v7 override conflict that also needs a human decision here.


Generated by Claude Code

Copy link
Copy Markdown
Member

🤖 pr-fix routine: blocked — marking pr-fix-stuck

Diagnosis (confirmed, single root cause): all 4 failing checks die at the install step:

error: lockfile had changes, but lockfile is frozen
note: try re-running without --frozen-lockfile and commit the updated lockfile

Dependabot changed package.json (@ai-sdk/azure ~3.0.77~4.0.26) but did not update bun.lock, which still pins 3.0.77. Every job that runs bun install --frozen-lockfile fails in 8–40s before doing any real work.

Why I couldn't fix it: the fix is bun install + commit the regenerated bun.lock. This routine's sandbox has no egress to registry.npmjs.org — every request returns 403 from the egress policy, so bun install cannot resolve @ai-sdk/azure@~4.0.26. Hand-editing bun.lock without verified integrity hashes and the real transitive tree would be reckless, so I did not attempt it.

Two things a human should look at:

  1. This is systemic, not per-PR. I spot-checked the sibling Dependabot PRs and they have the same shape — only a manifest file changed, no lockfile:

    Every open Dependabot npm PR in this repo (build(deps-dev): bump @types/node from 26.1.1 to 26.4.1 in /infra in the minor-and-patch group across 1 directory #1566chore(deps): bump @ai-sdk/azure from 3.0.95 to 4.0.26 #1576) will red-CI for this same reason. Worth fixing once at the Dependabot/bun-lockfile level rather than 11 times by hand.

  2. This bump also fights the pinned overrides. @ai-sdk/azure@4.x belongs to the AI SDK v7 line, but package.json overrides pin the v6 line:

    "ai": "~6.0.208",
    "@ai-sdk/provider": "~3.0.10",
    "@ai-sdk/provider-utils": "~4.0.30",
    "@ai-sdk/react": "~3.0.210"

    So even with a regenerated lockfile, bumping azure alone is unlikely to typecheck cleanly. This one probably needs to land as part of a coordinated v7 migration together with chore(deps): bump ai from 6.0.240 to 7.0.44 #1570 (ai 6→7), chore(deps): bump @ai-sdk/react from 3.0.242 to 4.0.47 #1569, chore(deps): bump @ai-sdk/amazon-bedrock from 4.0.145 to 5.0.38 #1572, chore(deps): bump @ai-sdk/google from 3.0.103 to 4.0.29 #1573, chore(deps): bump @ai-sdk/openai from 3.0.90 to 4.0.25 #1574, chore(deps): bump @ai-sdk/mcp from 1.0.52 to 2.0.20 #1575 — an architectural call, not an autonomous per-PR fix.

To unstick: run bun install on this branch from a machine with npm access and commit bun.lock (or fold this PR into a combined AI SDK v7 migration branch), then remove the pr-fix-stuck label. The routine will not pick this PR up again while the label is present.


Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code pr-fix-stuck pr-fix routine gave up — human attention needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant