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

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-registry-server	minor	v1.3.0 → v1.4.0

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

Compare Source

What's Changed

• Remove obsolete Vercel deploy hook for docs-website by @​rdimitrov in #​753
• Enrich ListRegistryEntries response with version metadata by @​rdimitrov in #​754
• Update anthropics/claude-code-action digest to e58dfa5 by @​renovate[bot] in #​756
• Update index.docker.io/library/golang Docker digest to 1e598ea by @​renovate[bot] in #​757
• Update go modules - autoclosed by @​renovate[bot] in #​758
• Release v1.4.0 by @​stacklokbot in #​755

Full Changelog: stacklok/toolhive-registry-server@v1.3.0...v1.4.0

---

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

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.3.0 → v1.4.0
Hand-written changes	1 commit(s)
Reference assets	refreshed (separate commit)
Gaps	0
Release contributors	1 auto-assigned (see sidebar)
Action required	Spot-check skill-authored prose for accuracy

Summary of changes

Auto-generated from commit titles -- skill did not write SUMMARY.md.

• Note no doc changes for toolhive-registry-server v1.4.0 (281bf01)

Run cost

Session	Turns	Cost (USD)
Generation	29	$1.5973
Editorial review	4	$0.4016
Total	33	$1.9989

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	Apr 24, 2026 2:57pm

[claude]

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

---

Upstream release docs — toolhive-registry-server v1.4.0

No hand-written doc changes needed. Wrote NO_CHANGES.md at the repo root explaining why.

• Phase 1: Discovery — fetched release, categorized 6 PRs
• Phase 2: Deep dive — verified the one product-facing PR against source at the tag
• Phase 3: Audit existing docs — impact map is empty for hand-written content
• Phase 4: Implementation — wrote NO_CHANGES.md; no prose edits
• Phase 5: Validation — skipped (no edits to validate)
• Phase 6: Committed and pushed

What shipped in v1.4.0

Only one product-facing change, PR #754: GET /v1/registries/{name}/entries admin response now includes title, description, createdAt, updatedAt, and position alongside the existing entryType, name, version, sourceName fields. Verified against internal/service/service.go at the v1.4.0 tag — the RegistryEntryInfo struct matches the PR description exactly.

The remaining PRs are infra-only: obsolete Vercel hook removal (#753), dependency bumps (#756, #757, #758), and the release cut (#755).

Why no prose edits

The admin list-entries response schema is documented solely via the auto-generated swagger at static/api-specs/toolhive-registry-api.yaml — which this PR's release workflow already regenerated (5 new field entries on RegistryEntryInfo, verified in the diff). The only prose reference to /v1/registries/{name}/entries in the docs is at docs/toolhive/guides-registry/authorization.mdx:310-314, where it's cited for authorization scoping rather than response shape. No edit warranted there.

No GAPS.md — the one product-facing PR's "why" is fully resolvable from its PR description (admin UI parity with /v1/sources/{name}/entries).
· Branch

[claude]

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

---

Editorial review — toolhive-registry-server v1.4.0

• Identify files changed by the previous upstream-release-docs commit
• Determine whether any in-scope docs need an editorial pass
• Post review outcome

Outcome: no editorial review needed

The previous session's commit (281bf01) touched exactly one file — NO_CHANGES.md at the repo root — which is a signal file for the next workflow step and is explicitly out of scope for this review.

The other two files in the PR are also out of scope:

• .github/upstream-projects.yaml — version bump managed by Renovate, not prose.
• static/api-specs/toolhive-registry-api.yaml — auto-generated swagger, regenerated from release assets.

No prose in docs/toolhive/** was modified, so there's nothing to edit. The upstream triage in the previous comment (only one product-facing PR, #754, surfaced purely through the regenerated swagger) stands.
· Branch

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.