Implement `registry-version-check` script
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 45/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 領域
- tooling
研究方向
Start by locating the registry's script entry points and the proposed Registry.Scripts.VersionCheck module. Read the most recent package set from the package-sets repository and inspect the registry's metadata directory. Done means identifying packages whose latest registry version exceeds the package-set version and logging those versions to the console.
由索引模型根據 Issue 內容生成。
描述
The packaging team regularly makes manual package sets releases. Manual releases are required, for example, when a package such as Halogen is upgraded. Invariably the new Halogen version will break other packages in the set, and so the Halogen release is not added at first. Over time the dependents upgrade to the new Halogen, at which point Halogen and its dependents can all be updated in one go to produce a new package set.
The packaging team needs to be able to tell what package versions have been uploaded to the registry and are more recent than the version of those packages in the package set. For example, if Halogen 6 is in the package set and Halogen 7 has been released (but could not be added automatically because it breaks downstream packages), then we need to be able to tell that there's a Halogen 7 release waiting to go into the package set.
To accomplish this, we need to add a new script to the registry. This script, most likely named Registry.Scripts.VersionCheck, should:
- Read in the contents of the most recent package set (this can be read from the
package-setsrepository for now, but it will use the registry in the future) - Read in the contents of the
metadatadirectory in the registry - Find all packages with a latest version higher than its version in the package set
- Log those package versions to the console for review
- 主要語言
- PureScript
- 星號
- 95
- 分支
- 79
- 平均合併
- 16 小時 13 分鐘
- 30 天內合併 PR
- 14
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
purescript/registry-dev 的其他 Issue
-
難度 5/5 一週以上 新手友好度 22/100
purescript/registry-dev#804 · 9 則留言 ·
維護者通常 1 天內回覆
-
A failed publish job permanently blocks retrying the same package version可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 4/5 3-5 天 新手友好度 48/100
purescript/registry-dev#793 · 5 則留言 ·
維護者通常 1 天內回覆
-
Implement search and versioned Prim docs for the new Pursuit可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#790 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Migrate Pursuit application to the monorepo可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉pursuit
purescript/registry-dev#789 · 1 則留言 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
-
Complete support for monorepos / subdir key and non-GitHub locations可能重新可做 @thomashoneyman 於 110 天前認領，目前沒有進行中的 PR。 未關閉
purescript/registry-dev#750 · 1 個 reaction · 已指派 1 人 ·
維護者通常 1 天內回覆
查看 purescript/registry-dev 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 72/100
ScoopInstaller/Extras#19364 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 70/100
osrep/Runes2P.jl#279 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
1.3 bug
難度 2/5 1-3 小時 新手友好度 78/100
-
normalizePropName strips `#` characters from Figma property names instead of only the `#id` suffix未關閉
難度 2/5 1-3 小時 新手友好度 72/100
figma/code-connect#419 ·