Skip to content

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

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

Copilot Fix(CI Failure): Bump pinned copilot-version default to 1.0.83#97
github-actions[bot] wants to merge 1 commit into
mainfrom
fix/ci-failure-34448413557

Conversation

@github-actions

Copy link
Copy Markdown

The scheduled version-pin-drift job in Test Copilot CLI (run 34448413557) failed because the CLI grew up faster than our pin.

💥 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

This is not a code regression — version-pin-drift is an intentional canary job (added in #81) that compares action.yml's pinned copilot-version default against @github/copilot@latest on npm, and only fails on the nightly schedule trigger (see test "${{ github.event_name }}" != "schedule" in the job). It correctly detected that the pin (1.0.80) had fallen behind the registry's latest release (1.0.83).

🛠️ Proposed Fix

Bump the pinned default from 1.0.80 to 1.0.83 in:

  • action.yml (copilot-version input default + description + inline comment)
  • README.md (options table + pinning examples)

Verified locally that python3 -c "import yaml; ...['copilot-version']['default']" now returns 1.0.83, matching npm view @github/copilot@latest version.

The scheduled version-pin-drift job failed because action.yml's pinned
default (1.0.80) had fallen behind the npm registry's @github/copilot
@latest (1.0.83). Bump the default and its docs/examples to match.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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.

1 participant