Skip to content

Align Dataverse plugin listing with upstream main - #5175

Open
saurabhrb wants to merge 2 commits into
github:mainfrom
saurabhrb:update-dataverse-plugin-description
Open

saurabhrb wants to merge 2 commits into
github:mainfrom
saurabhrb:update-dataverse-plugin-description

Conversation

@saurabhrb

@saurabhrb saurabhrb commented Oct 19, 2026 •

Copy link
Copy Markdown

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • I have read and followed the Guidance for submissions involving paid services.
  • My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory. (Not applicable: this updates an existing Microsoft-owned listing.)
  • The existing catalog entry and generated manifest follow the repository's required format.
  • The content is clearly structured and follows the existing external-plugin format.
  • I have tested the listing with GitHub Copilot CLI using an isolated marketplace and configuration directory. Installation reported all nine upstream skills; no Dataverse environment or credentials were required.
  • I have run npm start and verified that the README indexes are up to date.
  • I am targeting the main branch 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:

  • Use upstream's current description covering CRUD, bulk operations, queries, metadata, administration, security, environment management, and solution lifecycle.
  • Keep the listed version at 1.0.0, as requested and documented in upstream's marketplace maintenance guidance.
  • Match upstream keywords: dataverse, mcp, power-platform, and dynamics-365.
  • Regenerate the marketplace manifest, fixing the stale generated entry identified in review feedback.

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 pin

Preserve the existing GitHub source and plugin root:

{
  "source": "github",
  "repo": "microsoft/Dataverse-skills",
  "path": ".github/plugins/dataverse"
}

There is intentionally no source.sha or source.ref. The upstream repository's default branch is main; the listing therefore follows that branch rather than freezing installation at a commit or release tag. Upstream explicitly documents that the Awesome Copilot version field is cosmetic-only and does not need updating. It remains 1.0.0; it is not a Git revision selector.

Maintainer follow-up: the repository currently has conflicting requirements for existing unpinned listings:

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

  • Update to an existing plugin listing.
  • New plugin or skill content.

Validation

  • npm start passed; a second run produced identical marketplace output and no README changes.

  • npm run plugin:validate passed: 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:

    node --test eng/external-plugin-validation.test.mjs eng/external-plugin-quality-gates.test.mjs eng/lib/external-plugin-readme.test.mjs
  • Programmatic assertions confirmed that description, keywords, and the other non-version metadata match upstream main, the cosmetic listing version remains 1.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-xpp Finance and Operations skill.

  • git diff --check passed.

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.


DDCGenerated by DDC-Agent (Domain Dev Companion) v3.8.2 -- 2026-10-19 12:09 PDT (2026-10-19 19:09 UTC)

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@saurabhrb
saurabhrb requested a review from a team as a code owner October 19, 2026 18:15
Copilot AI max review requested due to automatic review settings October 19, 2026 18:15
@github-actions github-actions Bot added external-plugin Public external plugin submission plugin PR touches plugins labels Oct 19, 2026
@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

🔒 PR Risk Scan Results

Scanned 2 changed file(s).

Severity Count
🔴 High 0
🟠 Medium 0
ℹ️ Info 0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier
  • plugins/external.json is a high-risk path (automation, scripts, MCP config, hooks, or review policy)

Automated checks

Check Status Details
Line endings ✅ Passed Passed · logs
Spelling ✅ Passed Passed · logs
Generated README consistency ✅ Passed Passed · logs
Plugin and extension validation ✅ Passed Passed · logs
Plugin structure ✅ Passed Passed · logs
Risk scan ✅ Passed Passed · logs
Contributor reputation ✅ Passed Passed · logs
Duplicate resource scan ✅ Passed Passed · logs
PR quality signal ⏭️ Skipped Skipped by its workflow · logs
Canvas/plugin smoke test ✅ Passed Passed · logs

Review

  • Approvals: 0/1
  • Assigned reviewer: not assigned yet — comment /request-review to ask for one
  • Review target date: not set
  • Still needed: 1 more approval(s); an approval from a maintainer with admin or maintain permission
  • The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command Who What it does
/rerun-checks PR author, maintainers Re-runs failed or incomplete checks and re-evaluates this gate
/request-review PR author, maintainers Asks the review rotation to assign a reviewer (adds needs-reviewer)

Updated for b67be6a · gate run · This comment is maintained automatically — see submission gate docs.

@github-actions github-actions Bot added the awaiting-review Submission is waiting for automated intake validation label Oct 19, 2026
@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

🛑 External plugin PR checks failed (maintainer follow-up)

  • Changed entries detected: 1
  • Workflow state label: awaiting-review
  • Full logs: Download quality gate artifact
  • Status legend: ✅ pass · ⚠️ warning · 🛑 fail

Per-plugin quality summary

Plugin spec compliance (non-blocking) vally lint install smoke test version match ref/sha consistency canvas structure overall source tree
dataverse ⚪ not_run ⚪ not_run ⚪ not_run ⚪ not_run ⚪ not_run ⚪ not_run 🛑 fail repository

Gate output details

dataverse - vally lint (⚪ not_run)

Error: source.ref or source.sha is required for quality gates
    at resolveFetchSpec (file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-quality-gates.mjs:107:11)
    at cloneSubmissionRepository (file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-quality-gates.mjs:140:21)
    at runExternalPluginQualityGates (file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-quality-gates.mjs:1009:36)
    at file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-pr-quality-gates.mjs:135:23
    at Array.map (<anonymous>)
    at runExternalPluginPrQualityGates (file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-pr-quality-gates.mjs:127:52)
    at file:///home/runner/work/awesome-copilot/awesome-copilot/eng/external-plugin-pr-quality-gates.mjs:184:24
- dataverse: spec=not_run, vally-lint=not_run, install-smoke=not_run, version-match=not_run, ref-sha-consistency=not_run, canvas-structure=not_run, overall=infra_error

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

The generated marketplace manifest retains the old description, causing generated-file validation to fail.

1 open issue
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

Comment thread plugins/external.json
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>
Copilot AI max review requested due to automatic review settings October 19, 2026 19:19
@saurabhrb saurabhrb changed the title Update Dataverse plugin description Align Dataverse plugin listing with upstream main 🤖🤖🤖 Oct 19, 2026
@saurabhrb

Copy link
Copy Markdown
Author

/request-review

@github-actions

Copy link
Copy Markdown
Contributor

🙋 Added needs-reviewer. Reviewer routing is assigning a reviewer now.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

Maintainers must resolve the acknowledged conflict between default-branch tracking and quality-gate locator requirements.

No open issues 🎉

1 resolved since last review

Review effort: Max

@saurabhrb saurabhrb changed the title Align Dataverse plugin listing with upstream main 🤖🤖🤖 Align Dataverse plugin listing with upstream main Oct 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

awaiting-review Submission is waiting for automated intake validation external-plugin Public external plugin submission merge-risk:high needs-reviewer plugin PR touches plugins

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants