Skip to content

CLI: Update Go SDK to 5c91a27ba91634a48044544f67285782a68a9c80 - #257

Open
kernel-internal[bot] wants to merge 8 commits into
mainfrom
cli-coverage-update
Open

kernel-internal[bot] wants to merge 8 commits into
mainfrom
cli-coverage-update

Conversation

@kernel-internal

@kernel-internal kernel-internal Bot commented Sep 16, 2026

Copy link
Copy Markdown
Contributor

This PR updates the Go SDK dependency to the latest version.

SDK Update

  • Updated kernel-go-sdk to 5c91a27ba91634a48044544f67285782a68a9c80 (the v0.109.0 release)

Coverage Analysis

A full enumeration of SDK methods and CLI commands was performed. All 165 methods listed in the SDK's api.md were checked against the CLI command tree.

api.md is byte-identical between the previously pinned SDK version and 5c91a27, so no API methods, params, or fields were added — no new commands or flags are required by this bump.

Intentionally excluded: the six client.ConfigRegistry.* methods (List, Lookup, Resolve, Analyses.List, Analyses.Get, Analyses.Cancel) are marked x-cli-skip: true in openapi.yaml. This release also adds a ConfigRegistryAnalysisService.WaitForResult convenience helper over those same skipped endpoints, so it is likewise out of CLI scope.

Covered via streaming variants: six methods do not match cmd/ by name because the CLI uses the SDK's *Streaming variants — Deployments.FollowStreaming, Invocations.FollowStreaming, Browsers.Logs.StreamStreaming, Browsers.Telemetry.StreamStreaming, Browsers.Fs.Watch.EventsStreaming, and Browsers.Process.StdoutStreamStreaming.

No coverage gaps were found.

Also on this branch

Earlier commits on this evergreen branch carry the CLI-visible changes from preceding SDK bumps, re-verified against the v0.109.0 release:

  • kernel org limits get renders the OrgLimits concurrency fields (concurrent_sessions_used, concurrent_sessions_available).
  • The vaults cards create|update spec help describes card_id as an opaque AgentCard ID to pass through unchanged, matching the revised SDK contract (it no longer advertises a vc_... prefix).

Testing

go build ./..., go vet ./... and go test ./... all pass.

Smoke tested against the production API:

  • kernel org limits get (and -o json) — both concurrency fields render correctly
  • kernel vaults cards create --help — updated card_id text
  • kernel browsers list, kernel profiles list, kernel vaults list, kernel apps list, kernel proxies list

Triggered by: kernel/kernel-go-sdk@5c91a27
Reviewer: @stainless-app

Bumps the Go SDK from v0.105.1-0.20260916183112-dab5c0714192 to v0.107.0
(commit 6c9df7b).

The SDK surface is unchanged across this range: the previously pinned
pseudo-version already contained every feature commit in the 0.106.0 and
0.107.0 releases (persistent browser REPL, browser update start_url, config
registry, AgentCard preparation contracts, Link spend request errors). Only
release metadata differs, so no new commands or flags were required.

Coverage analysis: full enumeration of all 165 SDK methods in api.md against
the CLI command tree found no gaps. The six client.ConfigRegistry.* methods
are marked x-cli-skip in openapi.yaml and are correctly excluded. Param
fields without a dedicated flag were each verified as intentional:
- AuditLog{List,ExportChunk}Params.SearchUserID -> covered by --user-id
- AuditLogListParams.PageToken -> handled internally by ListAutoPaging
- AuthConnectionLoginParams.BrowserTelemetry -> deprecated, superseded by
  browser.telemetry, which --telemetry covers
- BrowserCurlParams.ResponseEncoding -> `browsers curl` streams raw bytes
  through its own HTTP client rather than the SDK method

Tested: go build ./..., go vet ./..., go test ./... (all 9 packages pass),
plus live API smoke tests of `browsers list`, `browsers create`,
`browsers repl` (verified top-level bindings persist across calls under a
stable REPL ID), `browsers update --start-url`, and `browsers delete`.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@socket-security

socket-security Bot commented Sep 16, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatedgolang/​github.com/​kernel/​kernel-go-sdk@​v0.107.0 ⏵ v0.108.1-0.20260917210657-3038f83eb3f773 +1100100100100

View full report

kernel-internal Bot and others added 2 commits September 17, 2026 18:50
Updates github.com/kernel/kernel-go-sdk from v0.107.0 to
v0.107.1-0.20260917184535-51d7fb82550d (commit 51d7fb8).

The upstream commit ("chore(stlc): seal custom-code tracking files")
contains no API surface changes -- the api.md/Go source diff between
v0.107.0 and 51d7fb8 is empty.

Coverage analysis: full enumeration of all 165 methods in api.md against
the CLI command tree (215 commands). All 159 non-skipped methods have a
corresponding CLI command; the 6 config-registry methods are marked
x-cli-skip: true in openapi.yaml. All params struct fields map to
existing flags, positional args, or are pagination internals handled by
the auto-pagers.

No new commands or flags were needed.

Tested: go build ./..., go vet ./..., go test ./... (all pass),
kernel browsers list, kernel profiles list against the live API.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update Go SDK to 6c9df7b5509837495c978dc99dfa494c5fd97591 CLI: Update Go SDK to 51d7fb82550d9dc79c9830d613225c907dae3f66 Sep 17, 2026
Updates github.com/kernel/kernel-go-sdk from
v0.107.1-0.20260917184535-51d7fb82550d to v0.108.0.

The only difference between the two module versions is the
internal/version.go version constant -- api.md and every public Go
source file are byte-identical, so there are no new API methods,
params, or fields to expose.

Coverage analysis: full enumeration of all 165 SDK methods in api.md
against all 176 CLI leaf commands found no gaps. 6 methods
(ConfigRegistry.{List,Lookup,Resolve} and
ConfigRegistry.Analyses.{Get,List,Cancel}) are marked x-cli-skip in
openapi.yaml and are intentionally absent. The remaining 159 all have
CLI commands. An automated SDK-param-field vs CLI-flag comparison
surfaced only naming false positives (e.g. proxy -> --proxy-id/--proxy-name,
tags -> --tag, timeout_seconds -> --timeout, hold_keys -> --hold-key) and
fields exposed as positional args; all were verified covered.

Tested: go build ./..., go vet ./... (clean), go test ./... (all pass),
and smoke-tested `kernel browsers list` and `kernel app list` against
the live API.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update Go SDK to 51d7fb82550d9dc79c9830d613225c907dae3f66 CLI: Update Go SDK to 3556e0031db27cbb1c2d0d321c814596e4d1921c Sep 17, 2026
Updates kernel-go-sdk to 6367486e6e06cdc3d9dc13c107dddca490e9b9bc.

That SDK change adds two response fields to OrgLimits:
concurrent_sessions_used and concurrent_sessions_available. Surface both
as rows in `kernel org limits get`. A null here means usage could not be
read rather than "unlimited", so these render as "unknown" instead of
reusing formatProjectLimitValue.

A full enumeration of the 165 methods in api.md found no missing
commands; the 6 config-registry methods are x-cli-skip. Param-field
audit found no missing flags: AuditLogListParams.PageToken is consumed
by the SDK auto-pager, AuthConnectionLoginParams.BrowserTelemetry is
deprecated in favor of browser.telemetry (already wired), and
BrowserCurlParams.ResponseEncoding does not apply because `browsers
curl` streams raw bytes over the browser HTTP client rather than calling
Browsers.Curl.

Tested: `kernel org limits get` and `-o json` against the live API
(1118 used + 882 available = 2000 max); full `go test ./...` passes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update Go SDK to 3556e0031db27cbb1c2d0d321c814596e4d1921c CLI: Update SDK to 6367486e6e06cdc3d9dc13c107dddca490e9b9bc and add org concurrency usage rows Sep 17, 2026
Bumps kernel-go-sdk to 3038f83eb3f7cc6a59059a0a04bdb111300ea77c, which
preserves credential field order: CredentialVaultItemSpec.Fields and
CredentialVaultItemSpecInputParam.Fields changed from a map keyed by name
to an ordered array, and each definition now carries a stable `name`.

- vaults_output.go: project spec.fields as an array (name, type, required,
  sensitive) instead of a keyed object, and look definitions up by name when
  deciding which non-sensitive values stay visible.
- vaults_credentials.go: document the ordered array and the name pattern,
  update the create example, note that update specs stay keyed by name,
  reject specs still using the object form with actionable guidance, and
  require every create field to carry a name. Error text never echoes values.
- README.md: same shape and ordering guidance.
- Tests: fixtures moved to the array shape; added coverage for field order
  reaching the API unchanged, the keyed-form error, and the missing-name error.

A full enumeration of api.md against the CLI command tree found no missing
commands. All config-registry and auth exchange endpoints are x-cli-skip.

Tested against the live API: vaults credentials create with out-of-alphabetical
field order (order preserved in the request and in get/list output), vaults
items get/list, vaults credentials update (keyed form, non-sensitive text/email
values still surfaced, sensitive omitted), vaults items invoke fill by field
name, and both new validation errors. Test vault, item, and browser deleted.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update SDK to 6367486e6e06cdc3d9dc13c107dddca490e9b9bc and add org concurrency usage rows CLI: Update SDK to 3038f83eb3f7cc6a59059a0a04bdb111300ea77c and adopt ordered credential fields Sep 17, 2026
Updates github.com/kernel/kernel-go-sdk to
v0.108.1-0.20260917213155-5cfceddfb1ea (5cfcedd).

The SDK change ("Accept opaque AgentCard vaulted card IDs") revises the
card_id contract on CardVaultItemSpecAgentcard: the value is an opaque ID
returned by AgentCard and must be passed through unchanged, without
assuming a prefix or format. The `vaults cards create|update` help text
still advertised a `vc_...` shape, so it is updated to match.

The CLI already forwards card_id verbatim inside the --spec JSON (there is
no --card-id flag), so no behavior change was needed; a regression test now
pins that prefixed, unprefixed and punctuated IDs all round-trip unchanged.

A full enumeration of all 165 SDK methods in api.md against the CLI command
tree found no missing commands. The six client.ConfigRegistry.* methods are
marked x-cli-skip in openapi.yaml and are intentionally absent. The
AgentCard and Link card spec field sets in the help text were verified
complete against the SDK param structs. No new params or fields were added
by this SDK bump, so no new flags were required.

Tested: go build ./..., go vet ./..., go test ./... (all pass);
vaults cards create --help (help renders on one line);
against production API: auth status, app list, vaults list,
vaults items list agentcard-vault, vaults items get agentcard-vault.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update SDK to 3038f83eb3f7cc6a59059a0a04bdb111300ea77c and adopt ordered credential fields CLI: Update SDK to 5cfceddfb1ea8ad60df078bd8e89b11ca1aaa8d2 and document opaque AgentCard card IDs Sep 17, 2026
Updates github.com/kernel/kernel-go-sdk from
v0.108.1-0.20260917213155-5cfceddfb1ea to the v0.109.0 release (5c91a27).

Coverage analysis: api.md is byte-identical across this bump, so no API
methods, params or fields were added and no new commands or flags are
required. The only source changes relative to the previously pinned
pseudo-version are the release version stamp and a new
ConfigRegistryAnalysisService.WaitForResult convenience helper. All six
/config-registry endpoints are marked x-cli-skip in openapi.yaml, so that
helper is intentionally out of CLI scope.

A full enumeration of all 165 api.md methods against the CLI command tree
found no gaps. The six methods that do not match cmd/ by name are covered
through the SDK's *Streaming variants (Deployments.FollowStreaming,
Invocations.FollowStreaming, Browsers.Logs.StreamStreaming,
Browsers.Telemetry.StreamStreaming, Browsers.Fs.Watch.EventsStreaming,
Browsers.Process.StdoutStreamStreaming). The OrgLimits concurrency fields and
the opaque AgentCard card_id help text, both landed earlier on this branch,
were re-verified against the release.

Tested: go build ./..., go vet ./..., go test ./... (all pass); against the
production API: org limits get (both concurrency fields render), vaults list,
vaults cards create --help.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@kernel-internal kernel-internal Bot changed the title CLI: Update SDK to 5cfceddfb1ea8ad60df078bd8e89b11ca1aaa8d2 and document opaque AgentCard card IDs CLI: Update Go SDK to 5c91a27ba91634a48044544f67285782a68a9c80 Sep 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants