[release/v7.6] Fix GitHub API rate limit errors in test actions#26492
Merged
TravisEz13 merged 1 commit intoPowerShell:release/v7.6from Nov 20, 2025
Merged
Conversation
Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: TravisEz13 <10873629+TravisEz13@users.noreply.github.com>
TravisEz13
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR backports a fix from #26489 to the release/v7.6 branch to resolve GitHub API rate limit errors in test actions. When multiple test jobs run concurrently, unauthenticated GitHub API requests are limited to 60 requests per hour, causing intermittent CI failures. By adding GITHUB_TOKEN authentication, the rate limit increases to 5,000 requests per hour, eliminating these errors.
Key Changes:
- Added
GITHUB_TOKENinput parameter to test actions for Windows and Unix platforms - Modified test actions to include Authorization headers when calling GitHub API
- Updated all CI workflows (Linux, macOS, Windows) to pass GITHUB_TOKEN to test jobs
Reviewed Changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/windows-ci.yml |
Added GITHUB_TOKEN parameter to all four Windows test jobs (unelevated/elevated CI and Others) |
.github/workflows/macos-ci.yml |
Added GITHUB_TOKEN parameter to all four macOS test jobs (unelevated/elevated CI and Others) |
.github/workflows/linux-ci.yml |
Added GITHUB_TOKEN parameter to all four Linux test jobs (unelevated/elevated CI and Others) |
.github/actions/test/windows/action.yml |
Added GITHUB_TOKEN input, created Authorization header, and applied it to GitHub API calls for DSC release fetching |
.github/actions/test/nix/action.yml |
Added GITHUB_TOKEN input, created Authorization header, and applied it to GitHub API calls for DSC release fetching |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jshigetomi
approved these changes
Nov 20, 2025
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.
Backport of #26489 to release/v7.6
Triggered by @TravisEz13 on behalf of @app/copilot-swe-agent
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Fixes intermittent CI failures when multiple test jobs run concurrently and hit GitHub API rate limits (60 req/hr unauthenticated). By adding GITHUB_TOKEN authentication, test actions get 5000 req/hr limit, preventing rate limit errors when fetching DSC releases during test setup.
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Original PR verified by running affected workflows in fork and confirming CI passes. Backport tested by applying clean cherry-pick to updated release/v7.6 branch - no conflicts encountered. The fix adds GitHub token authentication to API calls in test actions, preventing rate limit errors during concurrent CI runs.
Risk
REQUIRED: Check exactly one box.
Medium risk: Changes affect CI/CD test infrastructure across all platforms (Linux, macOS, Windows). However, the change is minimal (adding authentication headers), uses built-in GITHUB_TOKEN (no new secrets), and has been validated in master. Risk is isolated to test execution - does not affect production code.