Update stacklok/toolhive-registry-server to v1.4.5

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-registry-server	patch	v1.4.4 → v1.4.5

After this PR opens, .github/workflows/upstream-release-docs.yml adds source-verified content edits for the new release. For stacklok/toolhive, the same workflow also syncs reference assets (CLI help, Swagger) and regenerates the CRD MDX pages.

---

Release Notes

stacklok/toolhive-registry-server (stacklok/toolhive-registry-server)

v1.4.5

Compare Source

What's Changed

• Update go modules by @​renovate[bot] in #​795
• Release v1.4.5 by @​toolhive-release-app[bot] in #​796

Full Changelog: stacklok/toolhive-registry-server@v1.4.4...v1.4.5

---

Configuration

📅 Schedule: (in timezone America/New_York)

• 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: Never, 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.

---

Docs update for toolhive-registry-server v1.4.5

Note

Skill reported no doc-relevant changes for this release.
This PR only bumps the version pin and any pin_files edits.

At a glance

Upstream	stacklok/toolhive-registry-server v1.4.4 → v1.4.5
Hand-written changes	0 commit(s)
Reference assets	unchanged
Gaps	0
Release contributors	none in release range
Action required	—

Run cost

Session	Turns	Cost (USD)
Generation	32	$1.7186
Editorial review	4	$0.2581
Total	36	$1.9767

How this PR was built

Two Claude Opus sessions run per release: a generation pass
(upstream-release-docs skill, 6 phases) followed by a fresh-
context editorial pass (docs-review). Prettier/ESLint
auto-fixes are applied after.

Auto-synced paths — do not hand-edit these in review:

• docs/toolhive/reference/cli/
• docs/toolhive/reference/crds/
• static/api-specs/

If a "Gaps needing human context" section is present above,
each entry includes a paste-ready Helper prompt for local
Claude a reviewer can use to resolve the gap.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	May 21, 2026 10:03am

[claude]

Claude finished @renovate[bot]'s task in 2m 28s —— View job

---

Upstream release docs sync: toolhive-registry-server v1.4.4 → v1.4.5

• Phase 1: Discover the release (PRs, issues, commits)
• Phase 2: Deep-dive into significant changes
• Phase 3: Build impact map for documentation
• Phase 4: Audit existing docs (no edits needed)
• Phase 5: Skipped — no edits to validate
• Phase 6: Wrote NO_CHANGES.md for the workflow to surface

Result: no documentation changes required

This is a patch release that ships only:

• Update go modules toolhive-registry-server#795 (renovate) — Go module bumps. The only product-code change is removing initialization of the now-unused Groups field on UpstreamData in three internal/* files (internal/filtering/filter_service.go, internal/registry/testutils_upstream.go, internal/sources/api_upstream.go). The upstream UpstreamGroup type was deleted in stacklok/toolhive-core v0.0.20 as "chore: remove unused UpstreamGroup type".
• Release v1.4.5 toolhive-registry-server#796 (release bot) — automated version bump in VERSION, Chart.yaml, values.yaml, README.md.

Why this needs no docs

• No new or changed public API routes
• No new or changed CLI flags
• No new or changed Helm chart parameters or env vars
• No registry behavior or auth changes
• The dropped Groups field was already unused (no consumer relied on it)
• grep for 1.4.4, v1.4.4, UpstreamGroup, and upstreamGroups across docs/ returns zero matches, so there are no hardcoded version strings or removed-field references to sweep

The transitive bump of stacklok/toolhive from v0.27.2 → v0.28.0 brings substantial CLI/operator changes, but those land in this repo through the separate stacklok/toolhive upstream docs sync (already merged in bdd90bd's parent, e905248). They are not user-visible through the registry server's product surface.

NO_CHANGES.md was written at the repo root (gitignored signal file) for the workflow to surface in the PR body. No commits pushed because no docs needed editing.
· Branch

[claude]

Claude finished @renovate[bot]'s task in 25s —— View job

---

Editorial review: toolhive-registry-server v1.4.4 → v1.4.5

• Inspect files changed by the upstream-docs commit
• Determine whether any docs need an editorial pass

Result: no editorial review needed

The previous session correctly concluded no documentation changes were required for this patch release, and the only file modified by commit bdd90bd is .github/upstream-projects.yaml (a version-bump in an internal workflow config, not a documentation file). NO_CHANGES.md was left at the repo root as the handoff signal to the workflow.

There are no .md / .mdx files in scope, so /docs-review has nothing to operate on. Nothing to push.
· Branch