Proposal: Reimplement 'purs publish' in the registry

未關閉
  • 哪裡不對？
#525 10 則留言 3 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 1 天內回覆

@mikesol 已經在處理了。

開始於 2026年9月7日。

評估

這個 Issue 還沒有評估資料。

描述

pursuit

I think we should stop using purs publish and instead move that functionality into the registry. purs publish has many restrictions that prevent the registry from working properly, such as having to have a SemVer-compliant Git tag checked out with a clean source tree (except for the purs.json file). To support monorepos or non-GitHub locations we have to lift these restrictions. Rather than iterate on the compiler I think we should just do this in the registry, because then we can report better errors and not be tied in with compiler releases.

purs publish can stay in the compiler for non-registry users – the Pursuit API isn't changing – but I think eventually we will want to deprecate it altogether and have the registry be the direct pipeline to Pursuit.

We can do this because we already have, in the API pipeline:

  1. The dependency resolutions for the package
  2. The purs.json or spago.yaml manifest for the package
  3. The output directory produced by the compiler; we can also generate docs if need be.
主要語言
PureScript
星號
95
分支
79
平均合併
16 小時 13 分鐘
30 天內合併 PR
14

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

purescript/registry-dev 的其他 Issue

查看 purescript/registry-dev 的全部 Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。