Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 29, 2026

This PR contains the following updates:

Package Change Age Confidence
github.com/stacklok/toolhive v0.8.2v0.9.3 age confidence

Release Notes

stacklok/toolhive (github.com/stacklok/toolhive)

v0.9.3

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.9.2...v0.9.3

v0.9.2

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.9.1...v0.9.2

v0.9.1

Compare Source

What's Changed

Full Changelog: stacklok/toolhive@v0.9.0...v0.9.1

v0.9.0

Compare Source

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.8.3...v0.9.0

v0.8.3

Compare Source

Unified Versioning

Starting with this release, all ToolHive components now share the same version number:

  • CLI (thv)
  • Container images
  • Helm charts (toolhive-operator, toolhive-operator-crds)

The Helm charts now also reference container images with the same version tag, ensuring complete version alignment across the entire stack.

Why some versions appear to have "skipped"

You may notice that some components jumped version numbers:

Component Previous Version New Version
CLI v0.8.2 v0.8.3
Container images v0.8.2 v0.8.3
toolhive-operator chart 0.5.28 0.8.3
toolhive-operator-crds chart 0.0.106 0.8.3

This is expected. We unified all version numbers to simplify tracking and ensure consistency across the project. The actual changes in this release are patch-level—there are no breaking changes or major new features that would warrant the version jumps.

Benefits of unified versioning
  • Simpler compatibility tracking: All components with the same version are guaranteed to work together
  • Easier upgrades: No need to cross-reference compatibility matrices
  • Clearer release communication: One version number for the entire release
  • Chart and image alignment: Helm charts now deploy container images with matching version tags

Ref: #​1779

Future Simplification

We also have plans in the near future to remove the toolhive-operator-crds Chart in favour of a single toolhive-operator Chart. This is made possible by improvements in the CRD package and installation capabilities and allows us to simpify the experience for users by reducing the number of Charts they have to maintain their use of.

What's Changed

New Contributors

Full Changelog: stacklok/toolhive@v0.8.2...v0.8.3


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jan 29, 2026

ℹ️ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

  • 18 additional dependencies were updated
  • The go directive was updated for compatibility reasons

Details:

Package Change
go 1.25.5 -> 1.25.7
github.com/cedar-policy/cedar-go v1.4.0 -> v1.4.1
github.com/golang-jwt/jwt/v5 v5.3.0 -> v5.3.1
github.com/grpc-ecosystem/grpc-gateway/v2 v2.27.3 -> v2.27.7
github.com/lestrrat-go/httprc/v3 v3.0.3 -> v3.0.4
github.com/prometheus/common v0.67.4 -> v0.67.5
go.opentelemetry.io/otel v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/exporters/prometheus v0.61.0 -> v0.62.0
go.opentelemetry.io/otel/metric v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/sdk v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/sdk/metric v1.39.0 -> v1.40.0
go.opentelemetry.io/otel/trace v1.39.0 -> v1.40.0
golang.org/x/oauth2 v0.34.0 -> v0.35.0
golang.org/x/sys v0.40.0 -> v0.41.0
google.golang.org/genproto/googleapis/api v0.0.0-20251202230838-ff82c1b0f217 -> v0.0.0-20260128011058-8636f8732409
google.golang.org/genproto/googleapis/rpc v0.0.0-20251222181119-0a764e51fe1b -> v0.0.0-20260128011058-8636f8732409

@github-actions
Copy link

github-actions bot commented Jan 29, 2026

🔒 MCP Security Scan Results

⚠️ No MCP servers were scanned in this PR.

@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.8.3 fix(deps): update module github.com/stacklok/toolhive to v0.9.0 Feb 2, 2026
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch 2 times, most recently from d851360 to 9e6dca6 Compare February 4, 2026 21:09
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.9.0 fix(deps): update module github.com/stacklok/toolhive to v0.9.1 Feb 4, 2026
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 9e6dca6 to 6633d8f Compare February 6, 2026 17:02
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.9.1 fix(deps): update module github.com/stacklok/toolhive to v0.9.2 Feb 6, 2026
JAORMX
JAORMX previously approved these changes Feb 6, 2026
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 6633d8f to 7f9c2d6 Compare February 8, 2026 06:15
@renovate renovate bot force-pushed the renovate/github.com-stacklok-toolhive-0.x branch from 7f9c2d6 to e3ac801 Compare February 9, 2026 18:39
@renovate renovate bot changed the title fix(deps): update module github.com/stacklok/toolhive to v0.9.2 fix(deps): update module github.com/stacklok/toolhive to v0.9.3 Feb 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant