purescript / purescript/registry-dev
Deprecate support for legacy spago and bower manifests
Nobody has claimed this yet.
- Dominant language
- PureScript
- Stars
- 95
- Forks
- 79
- Avg merge
- 15m
- Merged PRs (30d)
- 1
Description
The registry launched on Feb 1, 2026 with continued support for bower.json files and spago.dhall files. This ensures that we can continue publishing e.g. core packages which use bower.json files. We intend to remove support for these manifest formats no earlier than August 1, 2026 and perhaps later. At that point packages using those manifest formats can no longer be published and they must switch to a purs.json format or another supported format such as spago.yaml.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names bower.json, spago.dhall, purs.json, and spago.yaml but no repository files or tests. Start by locating the registry's manifest-validation and publishing entry points, then define the removal boundary and verify that supported formats still publish while legacy manifests are rejected after August 1, 2026.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100