NPM version validation makes very difficult to automate registry publishing

未关闭
#1,792 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
49/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
go
领域
backend

调研方向

Start by tracing the registry's package publishing workflow and how it validates npm versions; the issue does not name specific files or tests. Compare the failure timing with npm's validation delay, then decide whether retrying or another approach fits. Done means publishing can handle that delay without requiring someone to rerun the workflow manually.

由索引模型根据 Issue 内容生成。

描述

bug

I have a workflow that publish my MCP server to npm and then to the registry...however since npm takes a while to validate the new package the registry constantly fails and I have to wait until npm "reacts" to the publication to re-run the workflow manually.

I wonder if there's something we could do to prevent this problem (not sure what, either a flag that says "I know this package will be there" or some automatic retry...not sure if you have any idea).

主要语言
Go
星标
7.4k
派生
1k
平均合并
17 小时 31 分钟
30 天内合并 PR
67

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

modelcontextprotocol/registry 的其他 Issue

查看 modelcontextprotocol/registry 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。