ci(docs): redeploy the site when install.sh changes
docs-gen publishes install.sh with the site, but the workflow only ran for docs/**, tools/docgen/** and tools/ludic-cli/**. v0.5.2 changed install.sh, CHANGELOG.md and VERSION — so nothing matched, no deploy ran, and the fix that release existed for was never served to anyone running the one-liner. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
parent
4aaf27c669
commit
f369fbd227
2 changed files with 10 additions and 0 deletions
|
|
@ -11,6 +11,10 @@ on:
|
|||
- 'docs/**'
|
||||
- 'tools/docgen/**'
|
||||
- 'tools/ludic-cli/**'
|
||||
# the site publishes the installer, so a change to it has to redeploy the
|
||||
# site — otherwise a fixed install.sh sits in main while the old one is
|
||||
# still what `curl … | sh` fetches
|
||||
- 'install.sh'
|
||||
- '.forgejo/workflows/docs.yml'
|
||||
workflow_dispatch: {}
|
||||
|
||||
|
|
|
|||
6
changes/docs-deploy-installer.md
Normal file
6
changes/docs-deploy-installer.md
Normal file
|
|
@ -0,0 +1,6 @@
|
|||
bump: patch
|
||||
type: ci
|
||||
The docs deploy triggers on a change to `install.sh`. The site publishes the
|
||||
installer, but the workflow's path filter did not mention it — so a release that
|
||||
only fixed `install.sh` left the old script live at the URL the landing page
|
||||
tells people to pipe into `sh`.
|
||||
Loading…
Add table
Add a link
Reference in a new issue