Skip to content

Migrate to Spago and update CI - #22

Open
thomashoneyman wants to merge 2 commits into
JordanMartinez:masterfrom
thomashoneyman:migrate-to-spago
Open

thomashoneyman wants to merge 2 commits into
JordanMartinez:masterfrom
thomashoneyman:migrate-to-spago

Conversation

@thomashoneyman

@thomashoneyman thomashoneyman commented Nov 3, 2026 •

Copy link
Copy Markdown

Support for bower.json and other legacy or unofficial registry formats ended on August 1, 2026. This PR migrates this library to the Registry-supported Spago format. It’s the same update the registry team rolled out across the core, contrib, web, node, halogen, and other organizations. At some point in the near future, the registry will stop publishing libraries that aren’t using a supported format and this package will be dropped from e.g. the package sets.

Alongside the manifest and directly dependent CI and test changes, this PR fixes command parsing with newer versions of parsing, preserving the registry’s existing >=10.2.0 <12.0.0 dependency range. The parser now stops explicitly at end-of-input rather than relying on many to swallow a failed argument parse. I suggest this only needs a patch release, unless you have other unreleased changes.

To complete the migration, you’d need to merge and then tag a new release, at which point the registry can pick up your library using the supported manifest. Thanks!

Comment thread spago.yaml
build:
strict: true
publish:
version: 5.0.1

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

With spago.yaml, the release version needs to be specified in the manifest. I’ve proposed a patch version here, so after merging you can tag this commit as v5.0.1. Of course you can also change it if you want to release as a different version!

Comment thread spago.yaml Outdated
- numbers: ">=9.0.0 <10.0.0"
- ordered-collections: ">=3.0.0 <4.0.0"
- parallel: ">=6.0.0 <8.0.0"
- parsing: ">=10.2.0 <10.3.0"

@thomashoneyman thomashoneyman Nov 4, 2026 •

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Restored the registry’s existing parsing range, >=10.2.0 <12.0.0, and fixed the command parser to stop explicitly at end-of-input using manyTill_ parseArg eof. This avoids relying on the pre-10.3.0 behavior of many. All 31 tests pass with each published version in this range: 10.2.0, 10.3.0, 10.3.1, 11.0.0, and 11.0.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant