Repository navigation
Conversation
Contributor
Author
|
Closing: custom code goes through the staging SDK repo. Will reopen there. |
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.
Summary
Fixes for the CLI coverage updater, found while reviewing the Node SDK's docs updater (kernel-node-sdk#225).
main, which happens before release-please creates the tag and GitHub release. On 2026-10-30 the run started at 06:02:31, andv0.138.0was tagged at 06:03:04.git describefound no tag, so the version fell back to the commit SHA, and CLI: Update Go SDK to 738369d524a3806832577f6793dde7eaf15c5725 cli#304 is titledCLI: Update Go SDK to 738369d5…. Hadgo getrun before the tag existed, it would have pinned a pseudo-version. The workflow now triggers onrelease: published, like the Node SDK's MCP updater, and takes the version from the release tag. Non-release pushes tomain, such as workflow changes, no longer start a full agent run.go.mod, so each run diffed only since the previous bot commit, and the PR body was replaced with that increment's report. CLI: Update Go SDK to 738369d524a3806832577f6793dde7eaf15c5725 cli#304 holds bumps from v0.131.0 through v0.138.0. The baseline now comes from CLIorigin/main'sgo.mod, so each run audits every release since main. The prompt tells the agent to keep earlier coverage on the branch and to describe the whole PR in its report.Testing
actionlintpasses. Shellcheck only reports the same info-level SC2086 findings asmain.go mod edit -jsonongit show origin/main:go.modfrom kernel/cli returns the pinned SDK version (v0.131.0).workflow_dispatch.