changelog - check whether releases are relevant
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- github, nuxt, typescript
调研方向
Start by tracing how package changelog currently selects and serves releases, then locate the latest release request and its version date. The issue proposes checking GitHub’s latest commit for changelog.md after a release is at least two weeks old, comparing dates, and serving the file when it is newer. Done means relevant changelog content is returned in that case; the issue does not name files or tests, so first identify the existing request path and its coverage.
由索引模型根据 Issue 内容生成。
描述
Describe the feature
Currently package changelog only checks whether releases are being used by a repo. not whether they're still relevant.
my current concept to fix this is as followed:
- when requesting the latest release, check the publish date against the package request version release date
- if the release is at least 2 weeks old, check changelog.md
- if changelog.md is newer (only by date, not time) serve the changelog.md instead.
currently the package I know that switched from releases to changelog.md is vue3-codemirror
What I've currently researched:
- for github you'll need to get the latest commit of a file and then either check last-modified header or
commit.commiter.datefield, the file api does also have the header but isn't accurate and doesn't have and anlastEditedfieldhttps://api.github.com/repos/{owner}/{repo}/commits?path={path_to_file}&page=1&per_page=1- example: https://api.github.com/repos/npmx-dev/npmx.dev/commits?path=README.md&page=1&per_page=1
- docs: https://docs.github.com/en/rest/commits/commits?apiVersion=2026-03-10#list-commits
Additional information
- Would you be willing to help implement this feature?
Final checks
- Read the contribution guide.
- Check existing issues.
- 主要语言
- TypeScript
- 星标
- 3.6k
- 派生
- 533
- 平均合并
- 4 天 13 小时
- 30 天内合并 PR
- 37
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
npmx-dev/npmx.dev 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
a11y front
难度 2/5 1-3 小时 新手友好度 67/100
npmx-dev/npmx.dev#2914 · 3 条评论 ·
维护者通常 1 天内回复
-
front i18n
难度 2/5 1-3 小时 新手友好度 64/100
npmx-dev/npmx.dev#2831 · 1 个 reaction ·
维护者通常 1 天内回复
-
back stale stale-to-close
难度 2/5 1-3 小时 新手友好度 62/100
npmx-dev/npmx.dev#2511 · 4 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
front needs discussion ux
难度 2/5 1-3 小时 新手友好度 65/100
npmx-dev/npmx.dev#2275 · 5 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
查看 npmx-dev/npmx.dev 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 66/100
db-ux-design-system/core-web#8613 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
bug internal-plugin pr-welcome upstream
难度 2/5 1-3 小时 新手友好度 78/100
dsh-tauri-desk/deepseek-harness-desktop#1225 · 1 条评论 ·
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
unjs/unhead#1027 · 1 个 reaction ·
维护者通常 1 天内回复