Repository navigation
ci: skip upstream release-channel checks in forks - #9
Merged
Merged
Conversation
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.
Release Sync has failed on eleven scheduled runs in this development fork because it has no published releases: GitHub returns HTTP 404, then the script reports an empty
Invalid release tag. The configured Chocolatey and WinGet identifiers belong to the upstream publisher.Restrict the verification job to
SteveTheKiller/KillerScanfor scheduled and manual runs. Check thegh apiexit code before parsing release metadata so actual upstream lookup failures retain a clear error. PR build/tests and package publishing workflows are unchanged.Validation: actionlint 1.7.12, PowerShell syntax parsing, six isolated cases of the actual release-lookup code (latest, explicit version, API failure, failed API with valid-looking payload, invalid tag, missing tag), and diff/privacy review passed. No packages were published or production installations changed.
Scheduled runs will use the fix after this PR reaches the fork's default branch. Historical failed runs remain; rerunning an old revision does not validate this fix.
Hosted validation on the PR head: PR build and tests passed all four jobs (application, engine-net48, engine-net10, speed-test-fixtures). A manual Release Sync run on the fix branch completed as
skipped, confirming the fork guard. The default-branch schedule is unchanged until merge.