A lightweight workflow pattern for checking Neexo Copilot plugin versions because Copilot plugins do not update automatically in consumer repositories.
AuthorNeexoCore
Updated
pluginsautomationgithub-actions
Why This Exists
Copilot plugins are updated manually with:
copilot plugin update <plugin-name>
Consumer repositories do not automatically receive plugin updates.
Weekly Check Pattern
Add a scheduled workflow that fetches the marketplace and prints available versions. Teams can extend it to open an issue or PR.
When a plugin update matters, update the local installed plugin with copilot plugin update, then verify Copilot Chat Diagnostics in VS Code.
Raw content
Copy this into your project — e.g. .instructions.md, .agent.md, or SKILL.md
## Why This Exists
Copilot plugins are updated manually with:
```bash
copilot plugin update <plugin-name>
```
Consumer repositories do not automatically receive plugin updates.
## Weekly Check Pattern
Add a scheduled workflow that fetches the marketplace and prints available versions. Teams can extend it to open an issue or PR.
```yaml
name: Check Copilot Plugin Updates
on:
schedule:
- cron: '0 9 * * 1'
workflow_dispatch:
jobs:
check:
runs-on: ubuntu-latest
steps:
- name: Fetch Neexo marketplace
run: |
curl -fsSL https://raw.githubusercontent.com/NeexoCore/awesome-neexo/main/.github/plugin/marketplace.json \
| jq -r '.plugins[] | "\(.name) \(.version)"'
```
## Team Process
When a plugin update matters, update the local installed plugin with `copilot plugin update`, then verify Copilot Chat Diagnostics in VS Code.