Repository navigation
fix: bump @v0-sdk/react from 3.0.7 to 3.0.8 in /apps/web - #2341
Open
dependabot[bot] wants to merge 4 commits into
Open
dependabot[bot] wants to merge 4 commits into
dependabot[bot] wants to merge 4 commits into
Conversation
Bumps [@v0-sdk/react](https://github.com/vercel/v0-sdk/tree/HEAD/packages/react) from 3.0.7 to 3.0.8. - [Release notes](https://github.com/vercel/v0-sdk/releases) - [Commits](https://github.com/vercel/v0-sdk/commits/v3.0.8/packages/react) --- updated-dependencies: - dependency-name: "@v0-sdk/react" dependency-version: 3.0.8 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
dependabot
Bot
added
dependencies
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
Contributor
Dependency ReviewThe following issues were found:
|
groupthinking
requested changes
Oct 28, 2026
groupthinking
left a comment
groupthinking
left a comment
Owner
There was a problem hiding this comment.
Review at head c09cf7ed: this PR changes apps/web/package.json without updating the root package-lock.json, and current-head build, lint, and frontend test checks fail. Reconcile the workspace lockfile with the manifest, then rerun the checks before approval.
… github.com:groupthinking/EventRelay into HEAD
Contributor
🔍 PR Validation✅ Current validation passed. |
github-actions
Bot
added
ci/cd
documentation
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
groupthinking
approved these changes
Oct 28, 2026
groupthinking
left a comment
groupthinking
left a comment
Owner
There was a problem hiding this comment.
Code review at exact head 60e2231e5abc6dba8ed25fc43516d5525ddb2ee1: the earlier requested change is resolved. The web manifest and root lockfile both resolve @v0-sdk/react@3.0.8 for the web app. The direct app v0@3.0.7 remains separate, and app source does not import @v0-sdk/react. I inspected the two-file diff and verified a clean npm 10.8.0 install, package resolution, 1,520 passing web tests (28 skipped), lint, typecheck and build. Current hosted build, lint, frontend tests and issue-link checks pass. This approval covers the code and lockfile correction only. The shared dependency-review job still fails after a 3-base/1-head snapshot warning and has no reliable evidence artifact. Keep this PR open and unmerged until that check passes with a complete dependency verdict on the final head.
This branch was successfully deployed
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 @v0-sdk/react from 3.0.7 to 3.0.8.
Release notes
Sourced from @v0-sdk/react's releases.
Commits
353b1a5Release v3.0.8 (#241)1c8baa0fix: support preview host mutations in React hook generation (#240)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)Codex verification — head
60e2231e5abc6dba8ed25fc43516d5525ddb2ee1The update now includes
apps/web/package.jsonand the rootpackage-lock.json. The web workspace resolves direct@v0-sdk/react@3.0.8. This branch was brought onto currentmain; the final no-content-change commit triggered checks against that corrected base.Local checks on the identical tree: clean npm 10.8.0
ci --ignore-scripts;npm ls @v0-sdk/react v0 --workspace=apps/web --depth=0;npm test --workspace=apps/web(1,520 passed, 28 skipped);npm run lint --workspace=apps/web;./node_modules/.bin/tsc --noEmit -p apps/web/tsconfig.json;npm run build --workspace=apps/web;git diff --check. The npm audit still reports 33 other findings and no@v0-sdk/reactorv0entry.Hosted checks on this head: 23 passed, 3 skipped, and
dependency-reviewfailed. Its run40690174834compared three base dependency snapshots with one head snapshot, retried for 300 seconds, then exceeded the evidence template size limit and uploaded no review artifact. Its partial output reported no new moderate-or-higher vulnerability, but the snapshot warning prevents a complete dependency verdict. Keep this PR open until the shared dependency evidence check is repaired and rerun successfully at the final head.