Skip to content

Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.83 - #96

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/ci-failure-34322322480
Closed

github-actions[bot] wants to merge 1 commit into
mainfrom
fix/ci-failure-34322322480

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 9, 2026

Copy link
Copy Markdown

The scheduled Test Copilot CLI workflow failed on the version-pin-drift job.

Turns out even our CI has version FOMO. 📌➡️🏃💨

https://github.com/austenstone/copilot-cli/actions/runs/34322322480/job/102371545359#step:4:5

💥 Error Log

##[warning]copilot-version default is pinned to 1.0.80 but @latest is 1.0.83
##[error]Process completed with exit code 1.

🕵️‍♂️ Diagnosis

The version-pin-drift job reads the pinned copilot-version default from action.yml and compares it against @github/copilot@latest on npm. It only hard-fails on schedule-triggered runs (so PRs just get a warning). The default was still 1.0.80 while npm @latest has moved on to 1.0.83, so the scheduled run failed as designed — this is a deterministic version-drift failure, not a code regression.

🛠️ Proposed Fix

Bump the pinned copilot-version default in action.yml from 1.0.80 to 1.0.83, and update the matching examples/table entries in README.md for consistency. Verified locally that the drift-check script now reports pinned=1.0.83 latest=1.0.83 (match).

The version-pin-drift job compares action.yml's pinned copilot-version
default against the npm @latest version and hard-fails on scheduled
runs when they diverge. The default was still pinned to 1.0.80 while
@github/copilot@latest is now 1.0.83, causing the scheduled CI run to
fail with:

  ::warning::copilot-version default is pinned to 1.0.80 but @latest is 1.0.83
  ##[error]Process completed with exit code 1.

Update the default and all doc examples to 1.0.83.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@austenstone

Copy link
Copy Markdown
Owner

Superseded by #108, which bumps the pin to 1.0.86 and caps the auto-fixer so a recurring failure can't open one PR per night. This PR targeted an already-superseded version.

@austenstone
austenstone deleted the fix/ci-failure-34322322480 branch September 20, 2026 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants