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

[renovate]

This PR contains the following updates:

Package	Update	Change
stacklok/toolhive-registry-server	patch	v1.2.1 → v1.2.2

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

Compare Source

What's Changed

• Persist claims on registry upsert conflict by @​blkt in #​746
• Release v1.2.2 by @​stacklokbot in #​747

Full Changelog: stacklok/toolhive-registry-server@v1.2.1...v1.2.2

---

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.

---

Content additions by upstream-release-docs

Source-verified against stacklok/toolhive-registry-server at tag v1.2.2 (was v1.2.1). Two Claude Opus sessions produced this update: a generation pass running the upstream-release-docs skill over all six phases, then a fresh-context editorial pass running docs-review over the changed files. Prettier and ESLint auto-fixes were applied afterward.

Note

The skill reported no doc-relevant changes for this
release. This PR only bumps the version reference
and any pin_files substitutions.

No doc changes for toolhive-registry-server v1.2.2

Release contains a single bug fix (PR
#746): the
UpsertRegistry SQL no longer drops the claims value on conflict, so
PUT /v1/registries/{name} now persists claim updates as already documented.
No new features, config, CLI flags, defaults, or API surface changes. The
existing docs already describe the intended behavior, so no edits are
required.

Review guidance

Machine-generated reference files under docs/toolhive/reference/cli/, static/api-specs/, and docs/toolhive/reference/crds/ are synced or regenerated from upstream release assets (separate commit, titled "Refresh reference assets") and should be spot-checked only. Commits authored by the skill contain hand-edited prose; review those for accuracy, not just style. If the "Gaps needing human context" section below is populated, each entry includes a Helper prompt for local Claude that a reviewer can paste verbatim into their local Claude Code session to resolve the gap. Fill those in before merging.

Reviewers below are non-bot commit authors in the release range who are also collaborators on this repo.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs-website	Ready	Preview, Comment	Apr 21, 2026 11:05pm

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

[github-actions]

Automated docs augmentation failed. Run: https://github.com/stacklok/docs-website/actions/runs/24745470509

Retry via the Upstream Release Docs workflow with pr_number=758 once the underlying issue is resolved.

[github-actions]

Automated docs augmentation failed. Run: https://github.com/stacklok/docs-website/actions/runs/24745672604

Retry via the Upstream Release Docs workflow with pr_number=758 once the underlying issue is resolved.

[claude]

Claude finished @rdimitrov's task in 1m 33s —— View job

---

upstream-release-docs for toolhive-registry-server v1.2.2

• Invoke /upstream-release-docs skill for stacklok/toolhive-registry-server v1.2.2
• Verify doc updates source-verified against upstream
• Commit and push changes (if any) - none required

Result: no doc changes needed.

The release contains a single functional PR:

• #746 - Persist claims on registry upsert conflict by @blkt

Source-verified against v1.2.2: it's a one-line SQL fix
(database/queries/registry.sql) that adds claims = EXCLUDED.claims to the
ON CONFLICT DO UPDATE SET clause, plus regenerated sqlc code and a regression
test. Previously, PUT /v1/registries/{name} silently dropped the new claims
value on conflict even though the timestamp advanced. The fix restores the
behavior the docs already describe.

No new features, config, CLI flags, defaults, deprecations, or API surface
changes. The claims concept is already documented in:

• docs/toolhive/guides-registry/intro.mdx
• docs/toolhive/guides-registry/configuration.mdx
• docs/toolhive/guides-registry/authorization.mdx

The other commit (#747) is the release PR itself - version bumps to
VERSION, Helm Chart.yaml, values.yaml, and the chart README. These are
infra and don't affect user-facing docs.

Per skill guidance, wrote NO_CHANGES.md at the repo root as the workflow
signal. The file is intentionally gitignored, so no commit is pushed.
| Branch: renovate/stacklok-toolhive-registry-server-1.x

[claude]

Claude finished @rdimitrov's task in 48s —— View job

---

docs-review for toolhive-registry-server v1.2.2

• Identify files changed by the upstream-release-docs commit
• Run editorial review over changed prose files
• Apply actionable fixes

Result: no prose to review.

The previous Claude session determined no doc changes were needed for this release and wrote NO_CHANGES.md as the handoff signal. The only file in this PR is .github/upstream-projects.yaml - a one-line Renovate version bump from v1.2.1 to v1.2.2, which isn't documentation.

No hand-edited prose was added under docs/toolhive/, so there's nothing in scope for a docs-review pass. The NO_CHANGES.md signal file is intentionally gitignored and not mine to touch.

Nothing to commit.
| Branch: renovate/stacklok-toolhive-registry-server-1.x

[github-actions]

Automated docs augmentation failed. Run: https://github.com/stacklok/docs-website/actions/runs/24750885214

Retry via the Upstream Release Docs workflow with pr_number=758 once the underlying issue is resolved.