feat(cd): adding MCP Publisher step to npm-publish - #1764
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the npm publish GitHub Actions workflow to additionally publish the MCP server package to the Model Context Protocol Registry as part of the release pipeline.
Changes:
- Adds a workflow step to download the
mcp-publisherbinary. - Adds a workflow step to authenticate via GitHub OIDC and publish to the MCP Registry.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
Suppressed comments (2)
.github/workflows/npm-publish.yml:51
- The workflow downloads and executes a binary from a
latestrelease URL without pinning a version or verifying integrity. This is a supply-chain risk and makes releases non-reproducible. Prefer pinning to a specific version tag and validating a provided SHA256 (or using a trusted action that verifies provenance) before executing the binary.
curl -fsSL "https://github.com/modelcontextprotocol/registry/releases/download/latest/mcp-publisher_$(uname -s | tr '[:upper:]' '[:lower:]')_$(uname -m | sed 's/x86_64/amd64/;s/aarch64/arm64/').tar.gz" | tar -xz -f - mcp-publisher; chmod +x mcp-publisher
packages/igniteui-mcp/igniteui-doc-mcp/README.md:199
- There appears to be a stray/duplicated section starting at "Or provide the URL via environment variable:" after the Links section, and the fenced code block is opened but not closed in the shown content. This will break Markdown rendering and is also confusing because remote-mode env var usage is already documented earlier. Remove this trailing fragment or move it into the Remote mode section and ensure code fences are properly closed.
## Links
- [Ignite UI](https://www.infragistics.com/products/ignite-ui)
- [Source repository](https://github.com/IgniteUI/igniteui-cli)
- [Issue tracker](https://github.com/IgniteUI/igniteui-cli/issues)
Or provide the URL via environment variable:
dkalinovInfra
previously approved these changes
Aug 4, 2026
dkalinovInfra
approved these changes
Aug 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Related Issue
Closes #
Type of Change
Affected Packages
igniteui-cli(packages/cli)@igniteui/cli-core(packages/core)@igniteui/angular-templates(packages/igx-templates)@igniteui/angular-schematics(packages/ng-schematics)@igniteui/mcp-server(packages/igniteui-mcp)Checklist
npm run test)npm run build)npm run lint)Additional Context