chore(deps): bump @ai-sdk/google from 3.0.103 to 4.0.29 - #1573
chore(deps): bump @ai-sdk/google from 3.0.103 to 4.0.29#1573dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@ai-sdk/google](https://github.com/vercel/ai/tree/HEAD/packages/google) from 3.0.103 to 4.0.29. - [Release notes](https://github.com/vercel/ai/releases) - [Changelog](https://github.com/vercel/ai/blob/main/packages/google/CHANGELOG.md) - [Commits](https://github.com/vercel/ai/commits/@ai-sdk/google@4.0.29/packages/google) --- updated-dependencies: - dependency-name: "@ai-sdk/google" dependency-version: 4.0.29 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1cfc6fb434
ℹ️ 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".
| "@ai-sdk/amazon-bedrock": "~4.0.120", | ||
| "@ai-sdk/azure": "~3.0.77", | ||
| "@ai-sdk/google": "~3.0.83", | ||
| "@ai-sdk/google": "~4.0.29", |
There was a problem hiding this comment.
This bump changes only package.json, but bun.lock still records the root dependency as @ai-sdk/google: ~3.0.83 and the resolved package as @ai-sdk/google@3.0.83. The CI and Docker build paths I checked run bun install --frozen-lockfile, so a clean checkout of this commit has an out-of-sync manifest/lockfile and fails during dependency installation before tests or builds can run. Please regenerate and commit bun.lock with the package bump.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed and correct — this is exactly the failure signature in CI. Test, Lint, and Type Check, Validate CDK Infrastructure, Auth Edge Production Artifact, and Unified Content PostgreSQL Lifecycle all die in ~12s at bun install --frozen-lockfile with error: lockfile had changes, but lockfile is frozen.
I can't carry out the fix from this autonomous routine. registry.npmjs.org is not on this environment's network egress allowlist — every request returns 403 with x-deny-reason: host_not_allowed, metadata and tarballs alike. The local Bun cache is empty and there is no node_modules, so nothing resolves offline either. Regenerating bun.lock would mean fabricating integrity hashes, which I won't do.
Flagging this PR pr-fix-stuck and leaving details for a human in a top-level comment, including what looks like the systemic cause. Thanks for the precise diagnosis.
Generated by Claude Code
|
🤖 pr-fix routine: blocked on lockfile regeneration — but I found the likely systemic cause This PRChanges exactly one line of Nothing about the failures is specific to Why this routine can't fix it (re-verified this fire, not assumed)
Regenerating the lockfile would require fabricating integrity hashes, which I won't do. 🔎 Likely root cause —
|
| Status | PRs |
|---|---|
Blocked on root bun.lock |
#1568, #1569, #1570, #1571, #1572, #1573, #1574, #1575, #1576 |
Blocked on infra/bun.lock |
#1566, #1567 |
| Genuinely green (no action) | #1562, #1564 |
That's 11 PRs blocked on one mechanical step.
What a human needs to do
- Per PR (works today): check out the branch, run
bun install(andcd infra && bun installfor the infra PRs), commit and push the updated lockfile. - Systemic (recommended): fix the
dependabot.ymlecosystem as above. Alternatively, allowlistregistry.npmjs.orgfor this routine's environment, which would let future fires regenerate lockfiles directly.
Separate concern once the lockfile is valid
@ai-sdk/google 3.0.103 → 4.0.29 is a major bump, and the repo is on ai@6.0.240 with #1570 separately proposing ai 6 → 7. Green CI here should not be read as an automatic merge signal — this wants a compatibility review sequenced against #1570.
The routine will not pick this PR up again until someone removes the pr-fix-stuck label.
Generated by Claude Code
krishagel
added
the
pr-fix-stuck
Claude
1 participant
Bumps @ai-sdk/google from 3.0.103 to 4.0.29.
Release notes
Sourced from @ai-sdk/google's releases.
Changelog
Sourced from @ai-sdk/google's changelog.
... (truncated)
Commits
eb3d1afVersion Packages (#18208)d8210b6chore: centralize record type guards in provider-utils (#18167)a56fbc0Version Packages (#18083)2ab3f34Version Packages (#18023)8bedb2cfix: prevent Google file uploads from failing with global Undici dispatchers ...d2d9324fix: preserve sampling-option behavior in Google Interactions (#17970)232a45aVersion Packages (#18004)c49380cfeat(openai,google): realtime translation providers (#17543)8fd84f0Version Packages (#17983)cd92c60Version Packages (#17912)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)