Copilot Fix(CI Failure): Pinned Copilot CLI version drifted behind npm latest - #109
Open
github-actions[bot] wants to merge 1 commit into
Open
github-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 whenever the pinned copilot-version default in action.yml falls behind @github/copilot@latest on npm. It detected pinned=1.0.80 vs latest=1.0.86 and failed the run (run #363, job version-pin-drift) as designed. Bump the default pin to 1.0.86 and update the matching README docs/examples. 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
Test Copilot CLIworkflow'sversion-pin-driftjob failed because the CLI version pinned as thecopilot-versiondefault inaction.ymlfell behind the version published to npm.Old wine in a new bottle, except the bottle expired:
1.0.80was still pinned while npm had already moved on to1.0.86. 🍷https://github.com/austenstone/copilot-cli/actions/runs/35572370193/job/106246524712#step:4:1
💥 Error Log
🕵️♂️ Diagnosis
This job (added in #81) intentionally fails on the
scheduletrigger whenever the pinned default inaction.ymlno longer matches@github/copilot@lateston npm, so drift gets caught automatically instead of silently going stale. The check ran and correctly detected that1.0.80(pinned) !=1.0.86(latest).🛠️ Proposed Fix
Bump the
copilot-versiondefault inaction.ymlfrom1.0.80to1.0.86, and update the matching examples/default value documented inREADME.mdso docs stay in sync with the actual default.