chore(deps): update @sanity/ui and resolve Sanity dependency conflicts#1679
chore(deps): update @sanity/ui and resolve Sanity dependency conflicts#1679renovate[bot] wants to merge 3 commits into
Conversation
86ccef5 to
8611d02
Compare
|
No dependency changes detected. Learn more about Socket for GitHub. 👍 No dependency changes detected in pull request |
ed6a936 to
da6cf73
Compare
e296b78 to
e5aaa3c
Compare
e5aaa3c to
9100fdd
Compare
7dee44d to
c9bfdb4
Compare
c3c93d1 to
a92cac4
Compare
b55c1ca to
133738c
Compare
c78ab13 to
4556815
Compare
4556815 to
6311596
Compare
6311596 to
77c0aa1
Compare
|
@copilot fix the failing check |
|
@copilot resolve the merge conflicts in this pull request and debug https://github.com/sanity-io/locales/actions/runs/27314858502/job/80693090255?pr=1679 |
Head branch was pushed to by a user without write access
Fixed in a1043e1. I resolved the failing test check by aligning the Sanity dependency resolution to a passing 5.17.1 set and updating the lockfile accordingly.
Done in a1043e1. I resolved the merge conflicts against main and debugged the failing run/job; the failure came from the Sanity upgrade path, and the dependency resolution is now adjusted so tests pass. |
|
@copilot resolve the merge conflicts in this pull request |
This PR now contains the following dependency updates:
^3.1.14→^3.2.0Additionally:
mainwere resolved inapps/studio/package.jsonandpnpm-lock.yaml.apps/studiodependencies were reconciled withmain(sanity,@sanity/vision, andgroqon the^6.1.0line).^5.17.1line where applicable.Release Notes