Fabrizio Ferrai

We should move forward with this, so it's in place for when we need it. The rough execution plan looks like this: - we'd add a policy document, probably/possibly embedded...

> Are you proposing that we re-introduce support for pre-releases? It's not an official proposal yet but I have warmed up to the idea after seeing the Registry deployed 😄

From today's discussion in the Registry Weekly: the side of the compiler that deals with publishing is adjacent to the docs, and that's a big chunk of code that might...

Thanks @thomashoneyman for digging into this! It seems problematic to me that the `reExport` list is always empty - surely the compiler should know what is being re-exported! I have...

> that would mean not being able to publish packages prior to whatever compiler version contains that fix That's ok? If you are publishing a package you're targeting the latest...

> might be a surprise for someone on a relatively recent compiler This is currently the first item on a list of things that we need to change to allow...

This is a Registry error, see the logs when we query the API using the job id from your logs: ``` $ curl https://registry.purescript.org/api/v1/jobs/c15beb1c-580f-4f2e-a269-c7d77a4f43bf | jq . { "createdAt": "2024-01-22T13:44:36.794Z",...

@thomashoneyman any clue what might be happening here? The [spago config](https://github.com/flip111/purescript-foldable-traversable-extra/blob/main/spago.yaml) seems alright

Ah indeed! Thanks Thomas. I guess both the registry and spago should check for the existence of the repo before doing their thing.

> Some kind of preflight check that the repository exists, and an error "Repository flip111/foldable-traversable-extra does not exist."? Yeah, errors from `git clone` are pretty generic, so we can offer...