@@ -409,11 +409,23 @@ jobs:
409409 # product, the registry entry is metadata. A registry-preview outage
410410 # must never block shipping. Re-run this job alone to retry — it does
411411 # not touch npm/PyPI, so retries are safe.
412+ #
413+ # It DOES depend on publish-final, which is the job that un-drafts the
414+ # release. Both used to need only publish-registries, so they raced: the
415+ # registry validates every package URL it is given by fetching it, and a
416+ # DRAFT release's assets are not publicly readable. In v0.10.3 the registry
417+ # ran 5s before the un-draft and was told its own .mcpb URL was a 404:
418+ # MCPB package '...codebase-memory-mcp-darwin-amd64.mcpb' is not publicly
419+ # accessible (status: 404)
420+ # The same URL served 200 once the release went public, and the job passed on
421+ # a plain re-run. Depending on publish-final keeps the documented intent
422+ # exactly — the registry still cannot block the release, it just runs after
423+ # the assets it validates actually exist to the outside world.
412424 publish-mcp-registry :
413- needs : [publish-registries]
425+ needs : [publish-registries, publish-final ]
414426 # Skipped for prereleases: the MCP Registry has no channel concept, so an
415427 # RC would present itself as the current version to every registry consumer.
416- if : ${{ !cancelled() && !failure() && needs.publish-registries.result == 'success' && !contains(inputs.version, '-') }}
428+ if : ${{ !cancelled() && !failure() && needs.publish-registries.result == 'success' && needs.publish-final.result == 'success' && !contains(inputs.version, '-') }}
417429 runs-on : ubuntu-latest
418430 permissions :
419431 id-token : write # GitHub OIDC auth to the MCP Registry
0 commit comments