stacklok / toolhive / 24738304706

Build # 24738304706

Build Type

push

github

Committed by web-flow

Commit Message

Unify docs-website release pipeline: new assets + retire dispatch chain (#4982)

* Bundle CRD manifests as a release asset

Adds a `thv-crds.tar.gz` tarball to each release containing the CRD
YAML manifests from `deploy/charts/operator-crds/files/crds/`.

Motivation: downstream consumers of the CRDs (notably
stacklok/docs-website, which generates per-CRD reference pages)
currently have to clone the entire toolhive repo at each release tag
just to read these 13 manifests. Shipping them as a ~94KB tarball
asset lets those consumers skip the clone and just `gh release
download` like they already do for `thv-cli-docs.tar.gz` and
`swagger.yaml`.

Purely additive — no changes to existing release assets or workflows.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Re-export toolhive-core schemas as release assets

Reads the toolhive-core version from go.mod at release time, downloads
the four JSON schema files from that version of stacklok/toolhive-core,
and ships them alongside toolhive's own release assets.

Motivation: downstream consumers (notably stacklok/docs-website)
currently have to replicate this logic: read go.mod, derive the core
version, then fetch from a different repo's release. Re-exporting the
schemas here makes toolhive's release self-contained — one `gh release
download` call gets everything.

Paired with https://github.com/stacklok/toolhive/pull/4982 (CRD
manifests as release asset); together these eliminate the need for
docs-website to clone toolhive or hit a second repo during its
release-doc regeneration.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Retire the docs-website repository_dispatch chain

docs-website no longer consumes `repository_dispatch: published-release`
events — its reference-doc regeneration now runs via a Renovate-driven
pipeline that reads the new `thv-crds.tar.gz` and re-exported core
schemas introduced earlier in this PR. See
https://github.com/stacklok/docs-we... (continued)

Coverage Stats

58546 of 88443 relevant lines covered (66.2%)

62.22 hits per line

Source File

Press 'n' to go to next uncovered line, 'b' for previous

Source Not Available