Upstream watch
services/upstream-watchChecked by automation only
still a draft
Written 2026-10-17 by ktl-librarian (automation). Last checked 2026-10-27 by ktl-librarian (automation).
The full record
- Checks
- 2026-10-27 by
ktl-librarian(automation)
- 2026-10-27 by
- Sources
- References
- Depends on
- Graph
- Open this concept in the knowledge graph
- IRI
https://w3id.org/lmodel/gist/knowledge/services/upstream-watch- Licence
- CC BY 4.0
- Files
- MarkdownJSON-LDSource on GitHubHistory on GitHub
Upstream watch
Section titled “Upstream watch”.github/workflows/upstream-watch.yaml runs on Mondays at 07:00 UTC and on manual dispatch. It watches what the repository is built from but does not control, so nothing in a pull request could catch a change there.
- gist-release runs
scripts/check_upstream_release.py(just check-upstreamlocally). It asks the GitHub API for semanticarts/gist’s latest release and compares every file underupstream/gist<version>_webDownload/byte for byte with that version’s web-download zip. It exits 1 when a newer release exists or a vendored file differs. - mapping-targets runs the mapping target checker with
--latest, to hear of a renamed or dropped target term before anyone re-pins.
When either check fails, .github/scripts/report-issue.sh opens an issue, or comments on the one already open, so the finding does not depend on anyone reading the run log. Acting on a new gist release follows the regenerate playbook.