fix: publish MCP Registry after crates and npm - #1908
Merged
patchloom-release[bot] merged 1 commit intoJul 22, 2026
Conversation
The 0.16.0 MCP Registry job timed out waiting for ownership markers because release:published fires when host creates the GitHub Release, about 15+ minutes before publish-npm and crates finish. Call publish-mcp-registry from release.yml after both package publishes succeed. Drop the race-prone release trigger; keep workflow_dispatch for recovery. Lengthen the marker wait and log HTTP status for CDN lag. Signed-off-by: Sebastien Tardif <sebtardif@ncf.ca>
patchloom-release
Bot
deleted the
fix/mcp-registry-publish-after-packages
branch
July 22, 2026 17:52
SebTardif
pushed a commit
that referenced
this pull request
Jul 23, 2026
🤖 I have created a release *beep* *boop* --- ## [0.17.0](patchloom-v0.16.0...patchloom-v0.17.0) (2026-07-23) ### Features * library doc_merge selector and embedder text I/O surface ([#1913](#1913)) ([0abfb40](0abfb40)), closes [#1909](#1909) [#1910](#1910) ### Bug Fixes * clarify init skip when AGENTS.md is not written ([#1922](#1922)) ([4323811](4323811)) * doc.merge catalog blurb mentions multi-doc selector ([#1917](#1917)) ([58e3f7a](58e3f7a)) * keep Permission denied and invalid_input on unreadable sole paths ([#1925](#1925)) ([cec22bd](cec22bd)) * load errors keep OS detail without double-wrap ([#1926](#1926)) ([8dd6987](8dd6987)) * publish MCP Registry after crates and npm ([#1908](#1908)) ([4ee64e8](4ee64e8)) * set error_kind on patch check multi-file JSON failures ([#1924](#1924)) ([322486c](322486c)) * sole unreadable path error without double-wrap ([#1916](#1916)) ([ec40404](ec40404)) * stop double-wrapping load_text_strict IO errors ([#1918](#1918)) ([8df2b48](8df2b48)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com> Co-authored-by: patchloom-release[bot] <291219740+patchloom-release[bot]@users.noreply.github.com> Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
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.
Summary
0.16.0 Publish MCP Registry failed: the workflow started on
release:publishedwhenhostcreated the GitHub Release (~17:10), while crates.io and npm only finished ~17:29. The marker wait (10 minutes) timed out before ownership markers existed.Fix
publish-mcp-registry.ymlfromrelease.ymlafterpublish-npmandcustom-publish-cratessucceedrelease:publishedtrigger; keepworkflow_dispatchfor recovery0.16.0 recovery
Manual
workflow_dispatchwithversion=0.16.0is running now (markers already live).Test plan