registry-dev
registry-dev copied to clipboard
Development work related to the PureScript Registry
This works ... ``` » git push Username for 'https://github.com': flip111 Password for 'https://[email protected]': Everything up-to-date ``` Doesn't work ``` » spago publish Reading Spago workspace configuration... ✅ Selecting package...
When a failure happens in the publish pipeline due to a problem with a package's source code, we report the bad files using their full filepath as we have it...
> Must contain only letters and digits, optionally separated by hyphens > Must begin with a letter or digit Are uppercase letters allowed? Is lower `é` a letter? Is lower...
Fixes #577. Fixes #255. Merging blocked by #696. The core problem solved here is identifying what compilers are compatible with a specific package version, such as `[email protected]`. We need this...
I think we should stop using `purs publish` and instead move that functionality into the registry. `purs publish` has many restrictions that prevent the registry from working properly, such as...
The PureScript registry is built to support packages using the [new manifest format](https://github.com/purescript/registry/blob/master/v1/Manifest.dhall) in a `.purs.json` file. However, we also support importing legacy packages from bower (#215), and the API...
In https://github.com/purescript/registry/pull/76#discussion_r495608601 we figured that using SemVer's "prerelease segment" for Trustees to publish versions, as the way the spec orders them is not the one we'd like. I'll report here...
A PureScript package normally is compatible with some, but not all, compiler versions. I suggest that we allow package authors to specify this information in their package manifest the same...
You can currently deprecate packages on Pursuit by setting the `keywords` field in your bower.json file to contain the keyword `pursuit-deprecated`. A package with this keyword automatically gets a banner:...
In https://github.com/purescript/registry/issues/336#issuecomment-1660974501 a package failed to commit and push metadata because the local checkout of the `registry` repo was behind the upstream by one commit. I don't think this should...