ci: disable hourly consume-spec cron until platform spec release exists - #2
Merged
Conversation
The hourly schedule fails every run with exit 4 (gh auth error) because tmsx-platform has no spec-v* release and PLATFORM_READ_TOKEN is unset (pending TECH-1117). Keep repository_dispatch + workflow_dispatch triggers. Also bump deprecated Node20 runner actions. Co-Authored-By: Claude Opus 4.8 (1M context) <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
1 participant
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.
Why
Since the
consume-specworkflows were merged, the hourlyschedulecron fires on all three SDK repos and fails every run (exit code 4).Root cause: the
Determine target spec versionstep runsgh release view -R tourmind-com/tmsx-platform, buttmsx-platformhas nospec-v*release yet andPLATFORM_READ_TOKENis not configured — soghexits with an auth error (exit 4), which Actions' defaultbash -eo pipefailpropagates. This is the credential-gated setup still pending in TECH-1117, not a workflow bug.Change
schedule:cron trigger untiltmsx-platformpublishes its firstspec-v*release andPLATFORM_READ_TOKENis set.repository_dispatch(real spec releases) andworkflow_dispatch(manual) triggers are unchanged, so the pipeline still works the moment it's wired.actions/checkout@v4→v5; plussetup-uv@v5→v6/setup-node@v4→v5where applicable).Re-enable
Uncomment the
schedule:block once the platform release + read token exist (the TECH-1117 P1 runbook).🤖 Generated with Claude Code