Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.82 - #90
Open
github-actions[bot] wants to merge 1 commit into
Open
Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.82#90github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
The scheduled version-pin-drift job compares action.yml's pinned copilot-version default against @github/copilot@latest on npm and fails the run when they diverge. @latest advanced to 1.0.82 while the default was still pinned at 1.0.80, causing run #326 to fail. Update the pinned default (and matching README example/table) to 1.0.82 to resolve the drift. 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 scheduled
version-pin-driftjob fails when the pinnedcopilot-versiondefault inaction.ymlfalls behind@github/copilot@lateston npm. It's a canary check to make sure the CLI pin doesn't get stale.It's not a bug in the traditional sense — the CI is doing exactly what it was built to do: yell when the pin drifts. Turns out even robots need reminders to update their software. 🤖📦
https://github.com/austenstone/copilot-cli/actions/runs/33726578439/job/91398634544#step:3
💥 Error Log
🕵️♂️ Diagnosis
The
version-pin-driftjob (added in #81) runs on a schedule and compares the pinnedcopilot-versiondefault inaction.ymlagainst the latest@github/copilotrelease on npm. When they diverge on a scheduled run, it intentionally fails (viatest "${{ github.event_name }}" != "schedule") to surface pin drift.@github/copilotreleased 1.0.82 while our default was still pinned to 1.0.80, tripping the check.🛠️ Proposed Fix
Bump the pinned
copilot-versiondefault inaction.ymlfrom1.0.80to1.0.82, and update the matching README table/example so docs stay in sync. Verified locally that the drift-check script now reportspinned=1.0.82 latest=1.0.82(match).