Repository navigation
Deprecate creation of legacy package sets #745
Description
Each package set created by the registry is also mirrored into the old packages.dhall format used by the legacy Spago package manager. Now that Spago is available at v1.0.0 we intend to deprecate support for legacy spago. That means we will no longer publish legacy package sets no earlier than August 1, 2026 — though the exact date isn't set.
Relates to #744.
Metadata
Metadata
Assignees
Labels
No labels
Activity
mikesol commentedon Sep 3, 2026
Lemme see if I can get this over the line
thomashoneyman commentedon Sep 7, 2026
This one has a somewhat hidden prerequisite — since the
contriblibraries all are still on legacy Spago, really they ought to be migrated to the new spago before we go ahead and remove legacy packages.dhall productionf-f commentedon Sep 26, 2026
...and moved to use version bounds rather than the package sets
thomashoneyman commentedon Oct 18, 2026
As per #744, all core, contrib, web, node, and halogen libraries have been migrated. We can move forward with the deprecation now.
thomashoneyman commentedon Oct 23, 2026
Follow-ups for retiring legacy package sets alongside #744 and the Dhall specification types:
packages.dhallforpsc-*tags. Preserve existing tags and release assets; stopping the registry producer does not disable this workflow.DHALL_TYPESconfiguration from purescript/registry daily jobs, and update its legacy-publishing documentation. Keep the daily importer, package transferrer, and modern package-set updater jobs.spago upgrade-setand writesspago.dhall.packages.jsonand compatibility-map updates, not onlypackages.dhall. Existing artifacts remain available, but publishing or retrying publication from an old tag requirespurs.jsonorspago.yaml.