Fabric MCP - Prepare for 1.0.0 GA release

[AmosHersch]

What does this PR do?

[Provide a clear, concise description of the changes]

[Add additional context, screenshots, or information that helps reviewers]

GitHub issue number?

[Link to the GitHub issue this PR addresses]

Pre-merge Checklist

• Required for All PRs
  • Read contribution guidelines
  • PR title clearly describes the change
  • Commit history is clean with descriptive messages (cleanup guide)
  • Added comprehensive tests for new/modified functionality
  • Created a changelog entry if the change falls among the following: new feature, bug fix, UI/UX update, breaking change, or updated dependencies. Follow the changelog entry guide
• For MCP tool changes:
  • One tool per PR: This PR adds or modifies only one MCP tool for faster review cycles
  • Updated servers/Azure.Mcp.Server/README.md and/or servers/Fabric.Mcp.Server/README.md documentation
  • Validate README.md changes running the script ./eng/scripts/Process-PackageReadMe.ps1. See Package README
  • For new or modified tool descriptions, ran ToolDescriptionEvaluator and obtained a score of 0.4 or more and a top 3 ranking for all related test prompts
  • For tools with new names, including new tools or renamed tools, update consolidated-tools.json
  • For renamed tools, follow the Tool Rename Checklist and tag the PR with the breaking-change label
  • For new tools associated with Azure services or publicly available tools/APIs/products, add URL to documentation in the PR description
• Extra steps for Azure MCP Server tool changes:
  • Updated command list in servers/Azure.Mcp.Server/docs/azmcp-commands.md
  • Ran ./eng/scripts/Update-AzCommandsMetadata.ps1 to update tool metadata in azmcp-commands.md (required for CI)
  • Updated test prompts in servers/Azure.Mcp.Server/docs/e2eTestPrompts.md
  • 👉 For Community (non-Microsoft team member) PRs:
    • Security review: Reviewed code for security vulnerabilities, malicious code, or suspicious activities before running tests (crypto mining, spam, data exfiltration, etc.)
    • Manual tests run: added comment /azp run mcp - pullrequest - live to run Live Test Pipeline

[Copilot]

Pull request overview

Prepares the Fabric MCP Server for a 1.0.0 GA release by bumping the server version and publishing consolidated release notes for both the server package and the VS Code extension.

Changes:

• Bumps Fabric.Mcp.Server version to 1.0.0.
• Adds a new 1.0.0 release section to the server and VS Code extension changelogs.
• Removes compiled changelog-entries/*.yaml files after merging their content into the main changelog.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
servers/Fabric.Mcp.Server/vscode/CHANGELOG.md	Adds a new 1.0.0 GA entry and backfills beta release history.
servers/Fabric.Mcp.Server/src/Fabric.Mcp.Server.csproj	Updates the server package version from beta to 1.0.0.
servers/Fabric.Mcp.Server/CHANGELOG.md	Replaces the unreleased beta section with a 1.0.0 GA release section and consolidated notes.
servers/Fabric.Mcp.Server/changelog-entries/1775162068769.yaml	Deletes a compiled changelog entry file.
servers/Fabric.Mcp.Server/changelog-entries/1774651569770.yaml	Deletes a compiled changelog entry file.
servers/Fabric.Mcp.Server/changelog-entries/1774379067978.yaml	Deletes a compiled changelog entry file.

[Copilot]

Changing Fabric.Mcp.Server to a non-beta public version (1.0.0) will cause eng/scripts/New-BuildInfo.ps1 to calculate the VSIX version from the VS Code Marketplace (it requires an existing 1.0.X series for major=1). If there are no published marketplace versions for major 1 yet, the build info generation fails (the script treats this as an illegal state for non-beta releases). Consider publishing a 1.0.0-beta.Y series first (so VSIX major 1 exists), or adjust the versioning/release tooling so the first GA can produce a deterministic VSIX version (e.g., 1.0.0).

Suggested change

	<Version>1.0.0</Version>
	<Version>1.0.0-beta.1</Version>

[Copilot]

The VS Code extension changelog is being updated with a 1.0.0 entry, but the packaging/versioning scripts may not actually produce a VSIX version of 1.0.0 for a non-beta public release (New-BuildInfo derives vsixVersion as 1.0.<nextPatch> from marketplace state). Please confirm the actual VSIX version that will be emitted for this release and align the VS Code CHANGELOG header accordingly to avoid mismatched marketplace version vs. changelog section.

Suggested change

	## 1.0.0 (2026-04-12)
	## 1.0.1 (2026-04-12)

[Copilot]

For markdown readability/consistency with the VS Code changelog entry, consider wrapping the --disable-caching option in backticks in the compiled server changelog as well (currently it’s plain text). This helps ensure it renders clearly as a literal CLI switch.

Suggested change

	- Add --disable-caching to server start options to disable caching. [[#2330](https://github.com/microsoft/mcp/pull/2330)]
	- Add `--disable-caching` to server start options to disable caching. [[#2330](https://github.com/microsoft/mcp/pull/2330)]