Thomas Honeyman

> A few thoughts on this - the distiction of "legacy package" vs "new package" is not really about any of the above - which I consider implementation details, as...

In the registry call @f-f reminded me that the https://github.com/purescript/pursuit-backups repository includes the compiler version used to publish to Pursuit, so that may be a reliable way to determine a...

We've had a discussion in core and I believe we have a consensus to apply a 0.13.0 cutoff.

We have a consensus to: 1. Drop package versions prior to PureScript 0.13.0 2. Drop packages altogether if they have no versions from 0.13.0 onward, freeing their names.

Starting up on this one! **Edit**: This is a bit tricky to implement after all, as it relates to #255, so I'm back to being paused for the time being.

The fix for this issue should include a test that verifies a failure in one part of the pipeline rolls back other changes such that we can re-issue the publish...

I don’t see how we could ensure the pipeline never fails — we can do our best to avoid failure, but we’re dealing with a remote git server so there’s...

Yea, we still want to have a check in the package upload pipeline that just verifies that the SPDX identifier you've asserted in your package manifest checks out against other...

> I'll note that really this is about having a slight convenience: right now package managers would have to fetch both the registry repo (for reading the metadata) and the...

> The reason why the registry-index is a git repository is actually for package-managers' convenience: in this way they can clone it once, and then get incremental updates. Having a...