Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.83 - #94
Open
github-actions[bot] wants to merge 1 commit into
Open
Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.83#94github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
The nightly version-pin-drift job fails whenever the pinned default in action.yml falls behind the @github/copilot package published to npm. The registry currently serves 1.0.83 while the default was still 1.0.80, so the job emitted a warning and exited non-zero on schedule. Bump the pinned default (and matching README examples) to 1.0.83 to clear 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 nightly `version-pin-drift` job failed because `action.yml`'s pinned `copilot-version` default (1.0.80) fell behind the version currently published to npm (1.0.83).
The @github/copilot package ships new releases faster than the sun sets, and apparently our pin took an extended vacation — turns out even version numbers need to touch grass occasionally. 🌱
https://github.com/austenstone/copilot-cli/actions/runs/34094608852/job/... (job:
version-pin-drift, step:Compare pinned default against registry latest)💥 Error Log
🕵️♂️ Diagnosis
This is not a broken workflow or transient error — it's the
version-pin-driftjob working exactly as designed (added in #81). It compares the pinnedcopilot-versiondefault inaction.ymlagainstnpm view @github/copilot@latest version, and intentionally fails on the nightlyscheduletrigger (but not on PRs) whenever they diverge, as a nudge to bump the pin. The registry moved from 1.0.80 → 1.0.83 since the pin was last updated.🛠️ Proposed Fix
copilot-versiondefault inaction.ymlfrom1.0.80to1.0.83.README.md(left the>=1.0.80floor-spec examples untouched since those remain valid regardless of latest).Verified
action.ymlstill parses correctly withyaml.safe_loadand the new default resolves to1.0.83.