From 83a015b57e427077cd50193891505c62b36f4863 Mon Sep 17 00:00:00 2001 From: Pablo Pardo Garcia Date: Wed, 5 Aug 2026 09:36:45 +0200 Subject: [PATCH] ci: dispatch docs bump to the renamed glassflow-docs repo The docs repo was renamed argus-docs -> glassflow-docs (GLA2-310). The GitHub API answers the old name with a 301, which curl --fail-with-body treats as success (it only fails on 4xx/5xx), so the v0.7.0 dispatch was dropped silently and no bump PR appeared. Point the dispatch at the new name. The docs workflow's weekly schedule remains the fallback; the 0.7.0 catch-up was triggered manually via workflow_dispatch. --- .github/workflows/release.yml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 0504db9..56d8c4c 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -39,11 +39,11 @@ jobs: - run: uv build - uses: pypa/gh-action-pypi-publish@dc37677b2e1c63e2034f94d8a5b11f265b73ba33 # release/v1 - # Tell argus-docs a new version shipped: its bump-api-reference workflow + # Tell glassflow-docs a new version shipped: its bump-api-reference workflow # opens the pin-bump + regenerated-reference PR. Fires only after the PyPI # publish succeeded (the docs workflow pip-installs the version). Needs # DOCS_DISPATCH_TOKEN — a fine-grained PAT (or GitHub App token) with - # contents:write on glassflow/argus-docs; GITHUB_TOKEN cannot dispatch + # contents:write on glassflow/glassflow-docs; GITHUB_TOKEN cannot dispatch # cross-repo. Skips gracefully while the secret is unset (the docs # workflow's weekly schedule is the fallback). dispatch-docs: @@ -64,7 +64,7 @@ jobs: curl -sS --fail-with-body -X POST \ -H "Authorization: Bearer $TOKEN" \ -H "Accept: application/vnd.github+json" \ - https://api.github.com/repos/glassflow/argus-docs/dispatches \ + https://api.github.com/repos/glassflow/glassflow-docs/dispatches \ -d "{\"event_type\":\"sdk-release\",\"client_payload\":{\"version\":\"$version\"}}" # Announce on Slack AFTER the PyPI publish succeeds, so the channel only