Repository navigation
ci(release-watch): keep the schedule from being disabled for inactivity - #20
Merged
Merged
Conversation
GitHub disables a public repository's scheduled workflows after 60 days without activity. release-watch was disabled on 2026-09-25, and the package fell four daemon releases behind. Each run now re-enables the workflow through the API, which resets that timer. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
GitHub disables a public repository's scheduled workflows after 60 days without repository activity.
release-watchwas disabled on 2026-09-25 (disabled_inactivity), so no new daemon release reached the package after that: four releases, up to v1.17.0.Each run now calls the "enable a workflow" API for itself first. That resets the inactivity timer without commits, the same method the keepalive-workflow project uses. The step only warns on failure, so it never blocks the watch. The job already has
actions: write.npm publishing is a separate problem: every
publish.ymlrun since July fails atnpm publishwithE404 Not Found - PUT https://registry.npmjs.org/pilotprotocol, which is npm's answer to a token that cannot publish the package.NPM_TOKENwas set on 2026-05-28, and npm caps write tokens at 90 days. Until the token is replaced, or trusted publishing is set up for this repository, the watcher stays disabled: enabled, it would dispatch a failing publish every 30 minutes.🤖 Generated with Claude Code