Repository navigation
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
🔒 PR Risk Scan ResultsScanned 2 changed file(s).
✅ No matching risk patterns were detected in changed files.
|
🚦 Submission status: 👀 Ready for reviewRisk tier: Why this tier
Automated checks
Review
Commands
Updated for |
🛑 External plugin PR checks failed (maintainer follow-up)
Per-plugin quality summary
Gate output detailsdataverse - vally lint (⚪ not_run) |
There was a problem hiding this comment.
🟡 Changes recommended
The generated marketplace manifest retains the old description, causing generated-file validation to fail.
What changed in this PR
Clarifies the Dataverse external plugin’s description in the Copilot plugin catalog.
Changes:
- Expands the listed capabilities and identifies MCP, CLI, and SDK workflows.
| File | Description |
|---|---|
plugins/external.json |
Updates the Dataverse plugin description. |
Review effort: Max
Preserve cosmetic version 1.0.0 and default-branch tracking. Align keywords and regenerate the marketplace manifest. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
/request-review |
|
🙋 Added |

Pull Request Checklist
npm startand verified that the README indexes are up to date.mainbranch for this pull request.Description
Refresh the existing Dataverse description and keywords from the current upstream plugin manifest on
main, while preserving the existing cosmetic marketplace version:1.0.0, as requested and documented in upstream's marketplace maintenance guidance.dataverse,mcp,power-platform, anddynamics-365.Only the Dataverse entry in the external catalog and its generated marketplace entry change. No plugin implementation, other catalog entries, or validation policies are changed.
Source tracking: upstream default branch (
main), not a SHA pinPreserve the existing GitHub source and plugin root:
{ "source": "github", "repo": "microsoft/Dataverse-skills", "path": ".github/plugins/dataverse" }There is intentionally no
source.shaorsource.ref. The upstream repository's default branch ismain; the listing therefore follows that branch rather than freezing installation at a commit or release tag. Upstream explicitly documents that the Awesome Copilotversionfield is cosmetic-only and does not need updating. It remains1.0.0; it is not a Git revision selector.Maintainer follow-up: the repository currently has conflicting requirements for existing unpinned listings:
source.ref: "main"is rejected by the existing validator.source.ref or source.sha is required for quality gatesfor this existing source shape.Please confirm the existing default-branch tracking for this Microsoft-owned listing, or provide a supported branch-tracking policy in the quality runner. This PR deliberately does not weaken the validation policy, disguise a mutable ref as a tag, or introduce an unwanted immutable pin.
Type of Contribution
Validation
npm startpassed; a second run produced identical marketplace output and no README changes.npm run plugin:validatepassed: 104 local plugins and 77 external entries. Existing catalog warnings, including the Dataverse unpinned-source warning, remain.Focused regression suite passed: 37 tests, zero failures:
Programmatic assertions confirmed that description, keywords, and the other non-version metadata match upstream
main, the cosmetic listing version remains1.0.0, the generated Dataverse entry equals the source entry, no ref/SHA pin is present, and every other external entry is unchanged.An isolated Copilot CLI installation using the exact updated entry succeeded and reported nine skills, including the current
erp-xppFinance and Operations skill.git diff --checkpassed.The local installation smoke test is not a claim that the hosted external-plugin quality gate passes; the locator-policy conflict above still needs maintainer resolution.
By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.