Fix keep-alive: point at relaton/support reusable workflow#7
Merged
Conversation
Replaces metanorma/ci/keep-alive.yml@main, whose leaf action gautamkrishnar/keepalive-workflow was blocked by GitHub on 2025-04-21 for ToS violation. Every monthly run since 2025-05-01 has failed. Depends on relaton/support#50.
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.
Summary
Repoints
.github/workflows/keep-alive.ymlfrom the brokenmetanorma/ci/keep-alive.yml@mainto a new in-org reusable workflow atrelaton/support. Addsworkflow_dispatch:so it can be tested manually, and a least-privilegepermissions: actions: writeblock.Root cause of the failures
The chain
keep-alive.yml → metanorma/ci/keep-alive.yml@main → gautamkrishnar/keepalive-workflow@v1has been failing every monthly run since 2025-05-01 with "Repository access blocked". Direct check:GitHub blocked the leaf action on 2025-04-21 for a Terms-of-Service violation (dummy commits to defeat the 60-day-inactivity policy). The block is repo-wide — no tag, branch, or SHA resolves. Re-pinning the version cannot fix it.
This is not a relaton org policy change and not a new GitHub Actions security feature, despite the misleading "access blocked" wording.
Companion change
Depends on relaton/support#50 which adds the new reusable workflow. That PR uses GitHub's official
actions/workflows/{id}/enableREST API instead of dummy commits — ToS-clean, no third-party action dependency.Merge order:
relaton/support#50first, then this PR.Part of a sweep
Same broken pattern exists in all
relaton-data-*repos withv2as default. Companion PRs across the family:relaton-data-etsi— #4 (pilot, fully verified)Follow-up
Update the
metanorma/cimastemplate to emit the new pattern so future regenerations don't undo this fix.🤖 Generated with Claude Code