Many people open bug reports or feature requests in the `actions/runner`
repository that are more generally about GitHub Actions. Often changes
in GitHub Actions are cross-cutting across multiple teams or feature
areas, so it's best if we direct people to the more general areas
(Actions Community Support or GitHub Feedback) so that we can get the
most eyes on the problem and give the quickest response.
From February 2021, in order to provide feedback on pull requests, Code Scanning workflows must be configured with both `push` and `pull_request` triggers. This is because Code Scanning compares the results from a pull request against the results for the base branch to tell you only what has changed between the two.
Early in the beta period we supported displaying results on pull requests for workflows with only `push` triggers, but have discontinued support as this proved to be less robust.
See https://docs.github.com/en/free-pro-team@latest/github/finding-security-vulnerabilities-and-errors-in-your-code/configuring-code-scanning#scanning-pull-requests for more information on how best to configure your Code Scanning workflows.
* Cross compile for win-x86, linux-arm, linux-arm64
* Build with actions instead
* Remove win-x86
* Preserve CURRENT_PLATFORM in dev.sh
* build.yaml
* Fix formatting. Remove piplines
* Use 4 space indent consistently
* x32 -> x86
* TEMP: Only test when platform === target runtime
Fix arm64 node externals url
* win-x86 externals
* Temporarily bench rhel
* Add RHEL6, skip L0 on arm for now
* Add stub for downloading new node externals when they are ready
* Remove RHEL6
* Package based on new runtime names
* Remove unused rhel from matrix includes
* Update release, add packages
* RID typo
* Cant cross test arm on x64 hosts
* New arch is a feature
Dont release x86 until we have an e2e test machine
* Fix version
* Get version from file to avoid exec error during package on x64 host for arm package
* Update Release Notes for 2.161.0 (#195)
* More cleanup
* Update release notes
