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

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-registry-server	patch	v1.4.12 → v1.4.13

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.13

Compare Source

What's Changed

• Bump toolhive-core to v0.0.28 by @​aponcedeleonch in #​840
• Release v1.4.13 by @​toolhive-release-app[bot] in #​841

New Contributors

• @​aponcedeleonch made their first contribution in #​840

Full Changelog: stacklok/toolhive-registry-server@v1.4.12...v1.4.13

---

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.13

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.12 → v1.4.13
Hand-written changes	0 commit(s)
Reference assets	refreshed (separate commit)
Gaps	0
Release contributors	1 auto-assigned (see sidebar)
Action required	—

Run cost

Session	Turns	Cost (USD)
Generation	39	$2.5138
Editorial review	5	$0.4163
Total	44	$2.9301

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:

• static/api-specs/
• docs/toolhive/reference/cli/ (toolhive only)

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	Jul 15, 2026 4:42pm

[claude]

Claude finished @renovate[bot]'s task in 3m 22s —— View job

---

Upstream release docs: stacklok/toolhive-registry-server v1.4.13

• Phase 1: Discovery — categorized release changes
• Phase 2: Deep dive — verified PRs against source
• Phase 3: Audit existing docs — no doc-relevant impact
• Phase 4: Implementation — none required (NO_CHANGES.md written)
• Phase 5: Validation — not applicable (no hand-edits)
• Phase 6: Review feedback — none

Summary

No hand-written documentation changes needed for v1.4.13.

Release contents:

• Bump toolhive-core to v0.0.28 toolhive-registry-server#840 (by @aponcedeleonch) — bumps toolhive-core from v0.0.26 to v0.0.28. The only source change is switching one import to the new mcpcompat/mcp compat shim in internal/kubernetes/types.go. Compat package is also named mcp, so no call sites change.
• Release v1.4.13 toolhive-registry-server#841 — the version-bump commit for the release itself (VERSION, Chart.yaml, values.yaml, helm-docs README).

User-visible surface:

• No new features, changed defaults, new config keys, CLI flags, or API routes.
• The auto-synced Registry Server swagger picked up a description change adding cargo to the list of common registryType values (static/api-specs/toolhive-registry-api.yaml +2/-2). The field is still typed as an unconstrained string, so this is descriptive only, not a schema change. No prose docs enumerate these types in a way that needs updating.
• The Enterprise Cloud UI entries page (docs/platform/enterprise-cloud-ui/administration/entries.mdx:29) does enumerate package types for its UI dropdown, but that reflects UI capability, not the Registry Server API — leaving it as-is.

NO_CHANGES.md has been written at the repo root for the calling workflow to splice into the PR body.
· branch

[claude]

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

---

Editorial review: toolhive-registry-server v1.4.13

• Identified files changed by the previous commit
• Confirmed no reviewable docs content in this PR

Result

No prose docs to review. The previous session concluded that v1.4.13 required no hand-written documentation changes and wrote NO_CHANGES.md. The only file touches in this PR are:

• .github/upstream-projects.yaml — config bump (out of editorial scope)
• static/api-specs/toolhive-registry-api.yaml — auto-synced spec (explicitly out of scope; regenerated from release assets)

No .md or .mdx files were modified, so there is nothing for a docs-review pass to act on. Leaving the branch untouched.
· branch