upstream-projects.yaml

# Human-maintained source-of-truth for upstream projects whose releases
# trigger doc-update PRs.
#
# Renovate watches `repo:` + `version:` pairs here as a custom-regex
# manager (see renovate.json) and opens a version-bump PR whenever an
# upstream releases a new tag. .github/workflows/upstream-release-docs.yml
# reacts to those PRs, shallow-clones the upstream, and adds
# source-verified content edits via the upstream-release-docs skill.
#
# For `stacklok/toolhive` specifically, most reference artifacts are
# declared as `assets:` below (synced by sync-assets.mjs) — plus one
# workflow-step in upstream-release-docs.yml that downloads the CRD
# manifests tarball and runs extract-crd-schemas.mjs + generate-crd-
# pages.mjs to produce our opinionated per-CRD MDX pages.
#
# You can also edit `version:` by hand (to backfill or reset) and
# dispatch the upstream-release-docs workflow manually in bootstrap
# or retry mode.

projects:
  - id: toolhive-registry-server
    repo: stacklok/toolhive-registry-server
    version: v1.3.0
    docs_paths:
      - docs/toolhive/guides-registry
      - docs/toolhive/concepts/registry-criteria.mdx
    # Files copied from the upstream repo at the pinned tag whenever
    # version: bumps. Source paths are relative to the upstream repo
    # root; destination paths are relative to this repo root. Keeping
    # the swagger locally (rather than referencing via jsdelivr) lets
    # the docs build offline and keeps the pin implicit in git.
    assets:
      - source: docs/thv-registry-api/swagger.yaml
        destination: static/api-specs/toolhive-registry-api.yaml

  - id: toolhive
    repo: stacklok/toolhive
    version: v0.23.1
    # toolhive is a monorepo covering the CLI, the Kubernetes
    # operator, and the vMCP gateway. It also introduces cross-
    # cutting features that land in concepts/, integrations/,
    # tutorials/, and hand-written reference pages. These entries
    # are hints, not constraints -- the skill's Phase 3 impact map
    # decides what actually changes. Hints focus Phase 2's source
    # reading so the skill doesn't re-scan unrelated areas.
    docs_paths:
      - docs/toolhive/guides-cli
      - docs/toolhive/guides-k8s
      - docs/toolhive/guides-vmcp
      - docs/toolhive/concepts
      - docs/toolhive/integrations
      - docs/toolhive/tutorials
      - docs/toolhive/reference/authz-policy-reference.mdx
    assets:
      - release_asset: swagger.yaml
        destination: static/api-specs/toolhive-api.yaml
      - release_asset: thv-cli-docs.tar.gz
        destination: docs/toolhive/reference/cli
        extract: tar-gz
      # toolhive-core schemas re-exported by toolhive at release time
      # (see stacklok/toolhive#4982). Previously downloaded from the
      # toolhive-core repo via a go.mod-derived version lookup.
      - release_asset: toolhive-legacy-registry.schema.json
        destination: static/api-specs/toolhive-legacy-registry.schema.json
      - release_asset: upstream-registry.schema.json
        destination: static/api-specs/upstream-registry.schema.json
      - release_asset: publisher-provided.schema.json
        destination: static/api-specs/publisher-provided.schema.json
      - release_asset: skill.schema.json
        destination: static/api-specs/skill.schema.json

  - id: toolhive-studio
    repo: stacklok/toolhive-studio
    version: v0.30.0
    docs_paths:
      - docs/toolhive/guides-ui

  - id: toolhive-cloud-ui
    repo: stacklok/toolhive-cloud-ui
    version: v0.5.1
    docs_paths: []