Copilot Fix(CI Failure): Bump pinned copilot-version to 1.0.82 - #88
Open
github-actions[bot] wants to merge 1 commit into
Open
Copilot Fix(CI Failure): Bump pinned copilot-version to 1.0.82#88github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
The scheduled version-pin-drift job fails when action.yml's pinned copilot-version default falls behind @github/copilot@latest on npm. Pinned was 1.0.80, latest is 1.0.82. Update the default and docs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.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
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.
The `version-pin-drift` job in the scheduled Test Copilot CLI workflow failed because the pinned default `copilot-version` in `action.yml` (`1.0.80`) fell behind the latest release on npm (`1.0.82`).
Turns out even a CI job whose entire purpose is "yell when we're out of date" can itself become... out of date. 🙃
https://github.com/austenstone/copilot-cli/actions/runs/33480678020/job/99769377284
💥 Error Log
```
##[warning]copilot-version default is pinned to 1.0.80 but @latest is 1.0.82
##[error]Process completed with exit code 1.
```
🕵️♂️ Diagnosis
The `version-pin-drift` job (added in #81) runs on a schedule and compares `action.yml`'s pinned `copilot-version` default against `@github/copilot@latest` on the npm registry. It intentionally fails (exit 1) whenever the pin has drifted, to prompt a manual bump. Since `1.0.80` was pinned, npm has published `1.0.82`, tripping the check. This is expected/by-design behavior for a drift detector, not a code regression — the fix is simply to bump the pin.
🛠️ Proposed Fix
Verified locally that `npm view @github/copilot@latest version` returns `1.0.82`, matching the new pin.