Move CI and releases to self-hosted runner pools - #14
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
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.
Move repository validation, SDK scenarios, releases, and maintenance to the Tart macOS ARM64 pool. Keep native installation coverage on our own Linux x64 and Windows x64 runners; no jobs use GitHub-hosted runners.
Install actionlint under RUNNER_TEMP so Tart does not need write access to /usr/local/bin. Compare the custom SDK path after macOS canonicalizes /tmp to /private/tmp. Guard source-executing jobs against external fork PRs on the self-hosted pools.
Validation: actionlint and git diff --check pass locally. Existing integration tests will verify the action on the new pools. This changes repository infrastructure only; action v1.1.0 remains unchanged.