Fabrizio Ferrai

I have this almost ready, with patches for codec-json, the registry, and spago itself

@cakekindel what's the usecase for this?

@sigma-andex if you cut a new tag it should be picked up by the registry, but switching out the `spago.dhall` with a `spago.yaml` should be good for future proofing

The registry currently has a cronjob to pick up all legacy packages once a day, but using `spago publish` will publish it immediately

Ah sorry, I meant to leave a review but I lost track of it

> From what I understand, the Y >= Z condition is already the case Ah yeah, it looks like I accidentally fixed this in #1228 😄 Tangential thought: looking at...

We are now printing a slightly better error: ``` Reading Spago workspace configuration... ❌ Couldn't parse Spago config, error: $.package.publish.location.gitUrl: No value found $.package.publish.location.githubRepo: No value found The configuration file...

I will close this for now since I am still holding the opinion that [I detailed above](https://github.com/purescript/spago/issues/1211#issuecomment-2052706247), but let's reopen it if the inconvenience gets too big 🙂

@hdgarrood how would you see [docs-search](https://github.com/spacchetti/purescript-docs-search) in the picture? I think we could actually replace the backend-side search from Pursuit with frontend-side search (using docs-search), e.g. see [Starsuit](https://spacchetti.github.io/starsuit/)

@hdgarrood I think that could be solved by having a richer search index right? I assume we don't want to enable all possible queries out there (since we'd need special...