Copilot Fix(CI Failure): Bump pinned Copilot CLI default to 1.0.81 - #84
Open
github-actions[bot] wants to merge 1 commit into
Open
Copilot Fix(CI Failure): Bump pinned Copilot CLI default to 1.0.81#84github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
The version-pin-drift job fails on schedule runs when the pinned default in action.yml lags behind the latest @github/copilot npm release. Run 33240058240 flagged pinned=1.0.80 vs latest=1.0.81. Update the pinned default (and README references) to 1.0.81 to clear the drift warning/failure. 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-driftjob in Test Copilot CLI failed on the scheduled run.Why does the pinned CLI version always end up one release behind? Because entropy has excellent release-cadence timing.
https://github.com/austenstone/copilot-cli/actions/runs/33240058240/job/... (job:
version-pin-drift, step:Compare pinned default against registry latest)💥 Error Log
🕵️♂️ Diagnosis
This is not a transient failure or a broken action — it's the intended behavior of the
version-pin-driftjob (added in #81), which intentionally fails onscheduleruns when the pinnedcopilot-versiondefault inaction.ymlno longer matches the latest@github/copilotrelease on npm.@github/copilotpublished1.0.81, so the job correctly flagged that the repo's pinned default (1.0.80) is stale.🛠️ Proposed Fix
Bump the pinned default in
action.ymlfrom1.0.80to1.0.81, and update the corresponding examples/table inREADME.mdto match. This clears the drift check without weakening it — the job will continue to catch future drift automatically on the next scheduled run after a new npm release.