npm lookups read registry errors as not published
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 停滞
- 技术栈
- node.js, typescript
调研方向
Read src/lib/registry.ts around isOnNpm and src/prerelease/prerelease-version.ts around fetchDevVersions; compare both with nfRegistryVersions in the same prerelease file. Check existing tests for these lookups and confirm they distinguish 404 from other non-2xx responses. Done means only 404 is treated as absent and other registry errors fail the step.
由索引模型根据 Issue 内容生成。
描述
Issue description
Both npm lookups read an error as "nothing there":
isOnNpm(src/lib/registry.ts#L13-L14) returnsfalsefor any non-2xx answer, including 429 and 5xx;fetchDevVersions(src/prerelease/prerelease-version.ts#L30-L38) returns[]on any error or non-2xx answer.
During an npm outage or a rate limit (traced, not run):
- a release re-run tries to publish a version that is already out and fails;
- an alpha whose committed version isn't on this branch's prefix restarts at
.0, and the publish fails on a taken version; - a beta publishes and silently deprecates nothing.
nfRegistryVersions in the same file already does it right: [] on 404 only, and an error on any other status.
Expected: only a 404 means "not published"; any other status fails the step.
Found by a read-only audit of main at 435a16b (first done at 046494f; no src/ file changed in between), report audits/actions-2026-11-11.md in the workspace repo.
Code sample
export const isOnNpm = async (name: string, version: string): Promise<boolean> =>
(await fetch(`https://registry.npmjs.org/${name}/${version}`)).ok;
Versions
- @nanoforge-dev/actions 3.3.0 (
mainat 435a16b) - Bun 1.3.14
Issue priority
Low (slightly annoying)
I have tested this issue on a development release
435a16b
- 主要语言
- TypeScript
- 星标
- 0
- 派生
- 0
- 平均合并
- 15 小时 51 分钟
- 30 天内合并 PR
- 21
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NanoForge-dev/actions 的其他 Issue
-
bug dependencies
难度 2/5 1-3 小时 新手友好度 65/100
NanoForge-dev/actions#137 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 73/100
NanoForge-dev/actions#136 ·
维护者通常 1 天内回复
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 75/100
NanoForge-dev/actions#135 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 62/100
NanoForge-dev/actions#134 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
NanoForge-dev/actions#131 ·
维护者通常 1 天内回复
查看 NanoForge-dev/actions 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
难度 1/5 1-3 小时 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
难度 2/5 1-3 小时 新手友好度 79/100
维护者通常 1 天内回复
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
难度 2/5 1-3 小时 新手友好度 65/100
growilabs/growi#12246 · 3 条评论 ·
维护者通常 1 天内回复
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 条评论 ·
维护者通常 1 天内回复