Hi everyone! I hope you all had a lovely 2025, and I wish you an even better 2026 
@thomashoneyman and I have been working day and night over the last few weeks to finally wrap up the Registry project and get the Registry and Spago out of alpha state. We are aiming to do all of that over the next few weeks.
What will happen
The PureScript Registry will leave alpha and move to GA.
There is one last breaking change that we need to ship, and since many of you are already using the new Registry since a while (through spago@next), we are trying to cause the least amount of disruption possible.
A summary of what’s happening under the hood: the new patch will enforce that all package versions solve and compile with at least one version of purs from 0.13 onwards. This change revealed some issues in how we computed dependency bounds for legacy packages. Specifically, fragmentation in the ecosystem led many packages to have a bower.json file, spago.dhall/packages.dhall file, and package-sets repository entry, often with no clear “canonical” manifest to choose among the three; the bounds we discovered for packages like these were overly-restrictive and caused several working packages to fail in solving or compilation.
We’ve reworked how we detect dependency lists and compute bounds when they are ambiguous, and things are working much better. We also now know what compiler versions each package version is compatible with – information we can push into Pursuit’s search functionality. However, this change modifies the contents of the package archives, and therefore we must reupload all package versions.
Not all package versions which existed in Bower will continue to be included in the registry. Specifically, any package version which cannot be solved / compiled with a compiler from 0.13.0 onwards (~early 2019) will be dropped from the registry. The full list of package versions that are present in Bower, GitHub, and all other sources but which won’t be in the registry are here.
At the same time Spago@next will also leave alpha and enter GA.
We will have a 1.0 release come out once the reupload has completed. spago publish will be broken on any version before this latest one, so we recommend you upgrade as soon as possible. The lockfile format is also changing, so expect to regenerate that; Nix users in particular will be affected and should upgrade and take note of the updates to the lockfiles.
Apart from the breakage to spago publish, previous versions of spago@next and spago-legacy should keep working as usual.
When is this happening
The Registry will be in an uncertain state (possibly down, possibly broken at times) from Friday 2026-01-30 18:00 UTC to Sunday 2026-02-01 22:00 UTC
We aim to have the reupload happen as soon as reasonably possible during the maintenance window, so that we can have some time to fix it up before everyone is back at the desks on Monday. We might be done quickly, or not, so this is all to say that if you can schedule your builds outside of these hours, then it might be a good idea to do so 
We will keep you posted on this thread on where we are with that, and please do report issues in here as well.
Fingers crossed, and I hope to be reporting some good news to you all soon