Publish a new version and bring it back to the package set

[m-bock]

I think this does not need any refactoring. Current master builds well with package set 43.3.0.

[natefaubion]

See purescript/registry-dev#662

I think we are waiting on a new ecosystem import to get correct dependencies.

[fsoikin]

Unless I'm misinterpreting something, it looks like the issue has been resolved quite some time ago. The registry now prunes test packages based on whether they're used in non-test code.

[natefaubion]

Is dodo in the registry? I have no idea. It does prune, but I don't think they ever did a reimport.

[fsoikin]

It's in the registry, but not in the package set. Also, the version that is in the registry (the latest one) has dependency ranges that don't work with the latest package sets.

[natefaubion]

The one in the registry isn't pruned (it has all its test dependencies listed), which is why it's probably not in the package set. That's what I mean by it wasn't reimported. Reimporting was going to happen but then never did. C'est la vie.

[fsoikin]

I think it can be reimported by just publishing another version and then opening a PR to the registry repo.

[natefaubion]

I understand :D My original comment was referring to an import that was supposed to happen, but never did, and most certainly won't :)

[fsoikin]

Sooo... Would you be able to do that at some point?

I'd offer to help, but this is not something that can be done with a code change, I'd need write permissions to the repo.

[fsoikin]

Thank you very much!