Update purescript-bound

[benjamin-hodgson]

{
  "name": "bound",
  "ref": "v0.6.0",
  "compiler": "0.15.9"
}

[benjamin-hodgson]

{
  "name": "bound",
  "ref": "v0.6.0",
  "compiler": "0.15.9"
}

[pacchettibotti]

The JSON input for this package update is malformed:

An error occurred while decoding a JSON value:
  Under 'Publish':
  At object key name:
  Under 'PackageName':
  Unexpected value "purescript-bound".

You can try again by commenting on this issue with a corrected payload.

[pacchettibotti]

Package source does not have a purs.json file. Creating one from your bower.json and/or spago.dhall files...

[pacchettibotti]

Verifying package...

[pacchettibotti]

Package is verified! Uploading it to the storage backend...

[pacchettibotti]

Successfully uploaded package to the registry! 🎉 🚀

[pacchettibotti]

Successfully uploaded package docs to Pursuit! 🎉 🚀

[pacchettibotti]

Mirrored registry operation to the legacy registry.

[stephen-smith]

I know this is closed, and probably the wrong place to ask, but how do I figure out which package-set I need to use in order to depend on this package (bound), I tried doing an upgrade-set and then removing my local fork from my packages.dhall, but the build failed saying the package was missing.

Trying to use psc-0.15.15-20240320 package-set AND purescript-bound.

Would be nice if Pursuit told me which package-set(s) included the version of the package it is showing me the documentation for. :/

[f-f]

@stephen-smith you're right - there are no facilities for this right now. This is something I wanted to implement in Spago since a long time, and we're actually most of the way there: we store the info, and it just need to be printed out. I opened purescript/spago#1218 to track this.