chore(deps): bump @ai-sdk/amazon-bedrock from 4.0.145 to 5.0.38 - #1572
chore(deps): bump @ai-sdk/amazon-bedrock from 4.0.145 to 5.0.38#1572dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@ai-sdk/amazon-bedrock](https://github.com/vercel/ai/tree/HEAD/packages/amazon-bedrock) from 4.0.145 to 5.0.38. - [Release notes](https://github.com/vercel/ai/releases) - [Changelog](https://github.com/vercel/ai/blob/main/packages/amazon-bedrock/CHANGELOG.md) - [Commits](https://github.com/vercel/ai/commits/@ai-sdk/amazon-bedrock@5.0.38/packages/amazon-bedrock) --- updated-dependencies: - dependency-name: "@ai-sdk/amazon-bedrock" dependency-version: 5.0.38 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: ba4b1b8ef6
ℹ️ 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".
| }, | ||
| "dependencies": { | ||
| "@ai-sdk/amazon-bedrock": "~4.0.120", | ||
| "@ai-sdk/amazon-bedrock": "~5.0.38", |
There was a problem hiding this comment.
Because bun.lock still resolves @ai-sdk/amazon-bedrock to 4.0.120 (bun.lock:7 and bun.lock:226), this manifest change leaves the dependency graph inconsistent. The checked CI and Docker paths install with bun install --frozen-lockfile (.github/workflows/ci.yml:36-37, Dockerfile:15-21), and bun install --help describes that flag as Disallow changes to lockfile, so this bump will fail or keep using the old package before it is tested/deployed. Please regenerate and commit bun.lock with the package change.
Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Confirmed and correct — this is the sole root cause of all 4 failing checks. bun.lock still resolves @ai-sdk/amazon-bedrock to 4.0.120 (bun.lock:7, bun.lock:226) while package.json now asks for ~5.0.38, so every job dies at bun install --frozen-lockfile before doing real work.
I can't apply the fix from this routine: the sandbox has no egress to registry.npmjs.org (verified this run — curl --noproxy '*' returns HTTP 403, and bun info @ai-sdk/amazon-bedrock@5.0.38 returns 403 Forbidden). Regenerating bun.lock requires resolving the real transitive tree and integrity hashes, so hand-editing it would be unsafe. Marking pr-fix-stuck with details in a top-level comment.
Two notes for whoever regenerates it:
- Use bun 1.2.23 (the pinned
packageManager) — this sandbox has 1.3.11, which would churn the lockfile format unnecessarily. - A regenerated lockfile alone probably won't make this green — see the
overridesconflict described in the top-level comment.
Generated by Claude Code
|
🤖 pr-fix routine: blocked — marking Diagnosis (confirmed, single root cause). All 4 failing checks — Test, Lint, and Type Check, Validate CDK Infrastructure, Auth Edge Production Artifact, Unified Content PostgreSQL Lifecycle — die at the install step within 10–45s: Dependabot changed Why I couldn't fix it. The fix is
Hand-writing A regenerated lockfile alone likely will not make this green. "ai": "~6.0.208",
"@ai-sdk/provider": "~3.0.10",
"@ai-sdk/provider-utils": "~4.0.30",
"@ai-sdk/react": "~3.0.210"The Recommended path. Treat #1568–#1576 as one coordinated AI SDK v6 → v7 migration branch ( Note for whoever regenerates the lockfile: use bun 1.2.23 (the pinned To unstick: run Generated by Claude Code |
krishagel
added
the
pr-fix-stuck
Claude
1 participant
Bumps @ai-sdk/amazon-bedrock from 4.0.145 to 5.0.38.
Release notes
Sourced from @ai-sdk/amazon-bedrock's releases.
Changelog
Sourced from @ai-sdk/amazon-bedrock's changelog.
... (truncated)
Commits
3fb63ebVersion Packages (#18234)52e22a7feat(bedrock): video input (#18235)eb3d1afVersion Packages (#18208)ebd31b8fix: warn when Bedrock cannot enforce strict tools and correctly route struct...a56fbc0Version Packages (#18083)2ab3f34Version Packages (#18023)232a45aVersion Packages (#18004)8fd84f0Version Packages (#17983)c8baafcVersion Packages (#17926)eb16508fix(provider/amazon-bedrock): omit toolstrictandoutput_config.formatf...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)