Copilot Fix(CI Failure): Resync pinned copilot-version default with npm latest - #99
Closed
github-actions[bot] wants to merge 1 commit into
Closed
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 compares action.yml's pinned copilot-version default against @github/copilot@latest on npm and fails when they diverge. The default was still pinned to 1.0.80 while the registry has published 1.0.83, so the job failed 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 in action.yml and its README documentation to 1.0.83 to resync with the latest published release. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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. |
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 failed on run 34679857990 becauseaction.yml's pinnedcopilot-versiondefault (1.0.80) had drifted behind the version published to npm (1.0.83).Why did the CLI cross the road? To get to the other semver. 🐔➡️📦
https://github.com/austenstone/copilot-cli/actions/runs/34679857990/job/103516345787#step:4
💥 Error Log
🕵️♂️ Diagnosis
The
version-pin-driftjob (added in #81) runs on a schedule and comparesaction.yml'sinputs.copilot-version.defaultagainst the@github/copilot@latestversion on the npm registry. It's designed to fail as soon as the two diverge, as a signal that the pinned default needs to be bumped. Nothing in the workflow or action logic is broken — this is an intentional drift alert, and the pinned default (1.0.80) is simply stale relative to the now-published1.0.83.🛠️ Proposed Fix
Bump the pinned
copilot-versiondefault from1.0.80to1.0.83in:action.yml(inputs.copilot-version.default)README.md(default value in the inputs table and the exact-pin example)Verified locally that the job's comparison logic (
PINNEDvsLATESTfrom npm) now matches (1.0.83==1.0.83), so theversion-pin-driftjob will pass on the next scheduled run.