Copilot Fix(CI Failure): version-pin-drift job failing on scheduled run - #85
Open
github-actions[bot] wants to merge 1 commit into
Open
Copilot Fix(CI Failure): version-pin-drift job failing on scheduled run#85github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
The version-pin-drift job fails scheduled runs whenever the pinned default in action.yml diverges from @github/copilot@latest on npm. npm now serves 1.0.82, so the nightly run failed with: ::warning::copilot-version default is pinned to 1.0.80 but @latest is 1.0.82 Process completed with exit code 1. Update the pinned default (and matching README docs) to 1.0.82 to resync with the registry and restore the green build. 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-drift` job in Test Copilot CLI (run 33298453176) failed on the scheduled trigger.
Every day the npm registry pushes a new version, and this poor job just gets told "nope, still not good enough." 😅
💥 Error Log
🕵️♂️ Diagnosis
The `version-pin-drift` job (added in #81) compares the pinned `copilot-version` default in `action.yml` against `@github/copilot@latest` on npm. It's designed to intentionally fail scheduled runs when the two diverge, so maintainers get an actionable signal instead of a silent warning. npm now serves `1.0.82` while `action.yml` was still pinned to `1.0.80`, so the check (correctly) failed:
`test "schedule" != "schedule"` evaluates false → non-zero exit → job failure.
This is not a transient/flaky failure — it's the drift-detection job doing exactly what it was built to do.
🛠️ Proposed Fix
Bump the pinned default from `1.0.80` to `1.0.82` in:
Verified locally that the drift check now matches:
```
PINNED=1.0.82 LATEST=1.0.82
MATCH - job would pass
```