chore(deps): bump Viam SDKs - #128
Open
viam-overwatch[bot] wants to merge 1 commit into
Open
Conversation
|
For security reasons, this PR must be labeled with |
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
1 participant
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.
Weekly automated bump of Viam SDK dependencies (Go:
go.viam.com/rdkand friends; Python:viam-sdk; TypeScript:@viamrobotics/*).Opened by the overwatch upgrade-viam-deps workflow. Claude attempted to fix breakage from the bump; the diff may include adjustments to call sites. Please review carefully.
📦 SDK version changes
🔴 High drift — the furthest-behind pin was 20.2 months old. This bump spans a lot of upstream change; review the call-site diff carefully.
go.viam.com/rdkv1.0.0(2026-07)v1.1.0(2026-07)go.viam.com/apiv0.1.566(2026-06)v0.1.574(2026-07)go.viam.com/testv1.2.4(2024-11)v1.2.5(2026-06)go.viam.com/utilsv0.6.6(2026-06)v0.10.1(2026-07)Versions read from the manifest diff; release dates from the Go module proxy, PyPI, and npm. Range specs (
^,>=) show their lower bound;?/unknownmeans the date couldn't be resolved.