26.4.1

Fix repository URL casing in package metadata

What changed

• PackageProjectUrl, RepositoryUrl, and PackageReleaseNotes in build/dependencies.props now use the canonical repo URL https://github.com/groupdocs/GroupDocs.Mcp.Core (with dots and proper casing) instead of the hyphenated form.
• Per-package README files (packed into each nupkg) updated with the same URL.

Why

The hyphenated form groupdocs/groupdocs-mcp-core works for git clone via GitHub's rename redirect, but deep links like /releases/tag/26.4.0 do not reliably redirect — users clicking the "Project website" link on the 26.4.0 NuGet package page land on a GitHub 404 instead of the release notes.

Migration / impact

None — API-surface unchanged. The nuget.org "Project website" and "Repository" links on future releases will resolve correctly.

Full Changelog: 26.4.0...26.4.1

26.4.0

Initial public release of GroupDocs MCP Core

What changed

• Four NuGet packages published together at version 26.4.0:
  • GroupDocs.Mcp.Core — file resolver, licensing, diagnostics, DI builder, core abstractions
  • GroupDocs.Mcp.Local.Storage — local filesystem IFileStorage implementation
  • GroupDocs.Mcp.AwsS3.Storage — Amazon S3 IFileStorage with presigned download URLs
  • GroupDocs.Mcp.AzureBlob.Storage — Azure Blob IFileStorage with SAS download URLs
• Multi-target: net8.0 and net10.0
• Environment variables read automatically by AddLocalStorage():
  GROUPDOCS_MCP_STORAGE_PATH, GROUPDOCS_MCP_OUTPUT_PATH (optional), GROUPDOCS_LICENSE_PATH
• CalVer versioning YY.MM.N — all four packages share one version.

Why

Shared infrastructure layer consumed by every GroupDocs product MCP server
(Metadata, Parser, Viewer, Conversion, etc.). Publishing Core first unblocks the
13 downstream product repos.

Migration / impact

First release — no migration required.

Full Changelog: https://github.com/groupdocs/GroupDocs.Mcp.Core/commits/26.4.0