Repository navigation
Conversation
The listing moved to getsigit/si, so this repo has no release-mcp-registry.yml and a release note that points at one sends the reader looking for a file that is not there. Replace it with what the flow actually does now, and add the two post-release checks that were missing: winget only goes live when its manifest PR merges, and each registry has to be verified by the name it publishes under (PyPI is `sigit-code`, not `sigit`). Co-Authored-By: siGit Code v1.7.5-acp <noreply@sigit.si>
![sigit-code-review[bot]](https://avatars.githubusercontent.com/in/3492899?s=60&v=4){kind=small}
There was a problem hiding this comment.
This change updates the release skill documentation to reflect the removal of the MCP Registry workflow and server.json from this repository, as the MCP Registry listing is now maintained in getsigit/si. It clarifies that the MCP server listing is not part of the siGit Code release flow, and corrects the workflow and checklist to match the current process. The checklist now explicitly notes that winget releases are not live until the PR is merged, and instructs to verify each registry by its actual published name, addressing past confusion with PyPI and other registries. No code changes are involved—this is a documentation-only update.
Automated review by siGit Code Review · commit 60996b8 · see the review dashboard
The MCP Registry listing moved to
getsigit/si(commit5aa0be3), so this repo no longer has aserver.jsonor arelease-mcp-registry.yml. The release skill still described both as part of the flow, which sends whoever is cutting a release looking for files that aren't there.This replaces that with what the flow actually does now, and fills two gaps in the checklist that cost time during 1.7.6:
release-winget.ymlrun only means a manifest PR was opened againstmicrosoft/winget-pkgs. Until a human merges it,winget installstill serves the previous version. The checklist now says to report it as "PR opened, awaiting review" with the link, not as done and not as a failure.sigit-code, notsigit— that name belongs to an unrelated package stuck at 0.0.58, so checking the wrong one looks like the release failed. Same for the rest: crates.iosigit, npm under both@getsigitand@smbcloud, NuGetSiGit.Code, plus the tap paths for Homebrew and Scoop. Also notes that crates.io 403s a barecurland needs aUser-Agent.Docs only — no code changes.