Add version check to skill workflows#30
Conversation
Add a version-check step to 'What's new for my project' and 'Find sessions' workflows. When the agent runs either workflow, it fetches the upstream plugin.json, compares versions, and nudges the user to update if behind. Bump plugin version to 1.0.2. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Adds a version-awareness nudge to key Microsoft Build skill workflows by checking the upstream plugin manifest version and prompting users to update when their installed copy is behind.
Changes:
- Added a “Version check” step to 3 workflows in
skills/microsoft-build/SKILL.md. - Bumped plugin manifest versions to
1.0.2for both GitHub Copilot and Claude plugin ecosystems.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| skills/microsoft-build/SKILL.md | Adds an upstream-version fetch/compare step to three workflows and appends an update nudge when outdated. |
| .github/plugin/plugin.json | Bumps Copilot plugin manifest version to 1.0.2. |
| .claude-plugin/plugin.json | Bumps Claude plugin manifest version to 1.0.2. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| 8. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features." | ||
|
|
||
| Be specific. "The new Azure Functions v4 streaming support affects your queue trigger in /api/process.ts" is useful. "There were updates to Azure Functions" is not. | ||
| Be specific."The new Azure Functions v4 streaming support affects your queue trigger in /api/process.ts" is useful. "There were updates to Azure Functions" is not. |
| - Documentation updates: what changed in the SDKs and services they use, with links to current docs | ||
| - Relevant sessions: event sessions that cover their technologies, sorted by relevance | ||
| 7. For high-confidence matches, offer to explain the migration path or impact on the developer's project | ||
| 8. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features." |
| - Documentation updates: what changed in the SDKs and services they use, with links to current docs | ||
| - Relevant sessions: event sessions that cover their technologies, sorted by relevance | ||
| 7. For high-confidence matches, offer to explain the migration path or impact on the developer's project | ||
| 8. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features." |
|
@TianqiZhang could you take a look at this one when you get a chance? |
| - Documentation updates: what changed in the SDKs and services they use, with links to current docs | ||
| - Relevant sessions: event sessions that cover their technologies, sorted by relevance | ||
| 7. For high-confidence matches, offer to explain the migration path or impact on the developer's project | ||
| 8. **Version check**: Fetch `https://raw.githubusercontent.com/microsoft/Build-CLI/refs/heads/main/.github/plugin/plugin.json` and read the `version` field. Compare it to the local `.github/plugin/plugin.json` version in this repo. If the remote version is higher, append to your response: "💡 A newer version of the Build CLI skill (v{remote}) is available. Run `/plugin update microsoft/Build-CLI` to get the latest sessions and features." |
There was a problem hiding this comment.
The local .github/plugin/plugin.json path is not a reliable source for the installed plugin version. During normal skill use, the current workspace is usually the user’s project, not this plugin repo, and users can directly install this skill via npx skills without installing plugin.
Until the industry agrees on a unified installed-plugin/skill versioning pattern, it's very difficult to make SKILL.md self-update.
What it does
Adds a version-check step to three SKILL.md workflows:
When the agent runs any of these workflows, it:
Changes
Why
Users have no way to know when skill updates are available. This is a lightweight, zero-infrastructure approach: the agent checks the upstream version on every workflow run and nudges if behind.