26.7.1

26.7.1 — Docker-first (OCI) publishing; NuGet size-gate

What changed

• Bumped the MCP package version from 26.7.0 to 26.7.1 (CalVer), including .mcp/server.json (both version fields) and the OCI identifier tag (ghcr.io/groupdocs-total/total-net-mcp:26.7.1).
• .mcp/server.json publishes as an OCI package (registryType: "oci", identifier: ghcr.io/groupdocs-total/total-net-mcp:<version>) instead of NuGet — GroupDocs.Total packs well over NuGet.org's 250 MB limit.
• publish_prod.yml: added a "Check nupkg size vs NuGet limit" step that sets an oversize output at the 250 MB threshold, and guarded the CodeSign / NuGet-push steps with if: oversize != 'true'. When oversized, the release still produces the GitHub Release, the Docker/GHCR image, and the MCP Registry entry (which waits on the GHCR image instead of the NuGet index).
• docker/Dockerfile: added LABEL io.modelcontextprotocol.server.name="io.github.groupdocs-total/groupdocs-total-mcp" (required for OCI registry validation) plus a revert-to-NuGet pointer comment.

Why

GroupDocs.Total's engine set makes the packed tool exceed NuGet.org's hard 250 MB limit, so a NuGet-tool install is impossible. Publishing the server as a Docker/OCI image (GHCR) and registering it in the MCP Registry via registryType: "oci" delivers the same server without the size ceiling. The size-gate keeps a single publish pipeline shared with the NuGet-sized products: it auto-detects oversize and skips only the NuGet-specific steps.

Migration / impact

Install via Docker/OCI rather than dnx/NuGet. Revert notes in publish_prod.yml and the Dockerfile describe restoring the NuGet path once (if) the packed size drops under 250 MB.

Full Changelog: https://github.com/groupdocs-total/GroupDocs.Total.Mcp/commits/26.7.1