Bump toolhive-core to v0.0.47 - #6646
Merged
Merged
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6646 +/- ##
==========================================
- Coverage 78.98% 78.91% -0.07%
==========================================
Files 782 782
Lines 78067 78067
==========================================
- Hits 61660 61606 -54
- Misses 16402 16456 +54
Partials 5 5 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
reyortiz3
force-pushed
the
bump-toolhive-core-v0.0.45
branch
from
September 11, 2026 16:36
1ad280f to
68eb621
Compare
toolhive-core v0.0.47 adds a plugin provenance field to registry/types, which flows into the generated skill schema. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
v0.0.47 marks toolhive-core/redis as a deprecated compatibility facade for redisconn (staticcheck SA1019), so switch every call site to redisconn.Config/NewClient directly. No behavior change: redisconn is a straight field-for-field superset of the old Config, and none of these call sites use cloud IAM auth. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
reyortiz3
requested review from
ChrisJBurns,
amirejaz,
aponcedeleonch,
blkt,
jerm-dro,
jhrozek,
rdimitrov and
tgrunnagle
as code owners
September 11, 2026 17:41
jhrozek
approved these changes
Sep 11, 2026
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
github.com/stacklok/toolhive-corefrom v0.0.43 to v0.0.47.redispackage referencedPoolSize/MaxActiveConnsfields onredisconn.Configthat weren't present in the publishedredisconnsubmodule (stuck at v0.0.1), so it failed to build. That was an upstream release-process bug — theredisconnsubmodule's tag was never cut when those fields were added.redisconn/v0.0.2was tagged, rootgo.modpins were corrected), andstacklok/toolhive-corecut a newv0.0.47release with everything consistent. This PR bumps straight to that release.go mod tidyalso promoted several transitive dependencies (e.g. sigstore/cosign signing, additional otel packages) to direct requires as a result of the newer toolhive-core version.toolhive-core/redispackage as a deprecated compatibility facade forredisconn(part of the same extraction work above). That surfaced 6staticcheckSA1019 failures acrosspkg/authserver,pkg/transport/session,pkg/vmcp/server, andpkg/runner. Migrated all call sites (12 files) fromredis.Config/redis.NewClienttoredisconn.Config/redisconn.NewClientdirectly — a straight rename with no behavior change, sinceredisconn.Configis a field-for-field superset of the oldConfigand none of these call sites use cloud IAM auth (DynamicAuth).provenancefield toregistry/types, which flows into the generated skill schema.Type of change
Test plan
task test)task lint) — 0 issuestoolhive-core@v0.0.47'sredispackage builds cleanly in an isolated module (go buildagainst the real published module, not a local replace)task docsregenerates cleanly with no diff (swagger/SDK now match)API Compatibility
v1beta1API, OR theapi-break-allowedlabel is applied and the migration guidance is described above.Does this introduce a user-facing change?
No.
Special notes for reviewers
redis→redisconnmigration is mechanical (import path + 4 renamed symbols:Config,NewClient,SentinelConfig,TLSConfig), verified againstredis.Config's own translation method in the deprecated facade to confirm the field mapping is 1:1.redisconnmigration, to keep the diff easy to review separately from the version bump itself.🤖 Generated with Claude Code