Closed m-bock closed 11 months ago
Package source does not have a purs.json file, creating one from your spago.yaml file...
Converted your spago.yaml into a purs.json manifest to use for publishing:
"name": "marked",
"version": "0.1.0",
"license": "BSD-3-Clause",
"location": {
"githubOwner": "thought2",
"githubRepo": "purescript-marked"
},
"dependencies": {
"dts": ">=1.0.0 <2.0.0",
"either": ">=6.1.0 <7.0.0",
"foreign-object": ">=4.1.0 <5.0.0",
"integers": ">=6.0.0 <7.0.0",
"labeled-data": ">=0.2.0 <0.3.0",
"literals": ">=1.0.2 <2.0.0",
"maybe": ">=6.0.0 <7.0.0",
"newtype": ">=5.0.0 <6.0.0",
"nullable": ">=6.0.0 <7.0.0",
"prelude": ">=6.0.1 <7.0.0",
"ts-bridge": ">=4.0.0 <5.0.0",
"unsafe-coerce": ">=6.0.0 <7.0.0",
"untagged-union": ">=1.0.0 <2.0.0",
"variant": ">=8.0.0 <9.0.0",
"variant-encodings": ">=2.0.0 <3.0.0"
}
}```
Package is verified! Uploading it to the storage backend...
Successfully uploaded package to the registry! 🎉 🚀
Could not publish your package to Pursuit because an error was encountered (cc: @purescript/packaging): Pursuit publishing failed with an HTTP error: fetch failed
{ "name": "marked", "ref": "v0.1.1", "compiler": "0.15.10", "location": { "githubOwner": "thought2", "githubRepo": "purescript-marked" } }
Package source does not have a purs.json file, creating one from your spago.yaml file...
Converted your spago.yaml into a purs.json manifest to use for publishing:
"name": "marked",
"version": "0.1.0",
"license": "BSD-3-Clause",
"location": {
"githubOwner": "thought2",
"githubRepo": "purescript-marked"
},
"dependencies": {
"dts": ">=1.0.0 <2.0.0",
"either": ">=6.1.0 <7.0.0",
"foreign-object": ">=4.1.0 <5.0.0",
"integers": ">=6.0.0 <7.0.0",
"labeled-data": ">=0.2.0 <0.3.0",
"literals": ">=1.0.2 <2.0.0",
"maybe": ">=6.0.0 <7.0.0",
"newtype": ">=5.0.0 <6.0.0",
"nullable": ">=6.0.0 <7.0.0",
"prelude": ">=6.0.1 <7.0.0",
"ts-bridge": ">=4.0.0 <5.0.0",
"unsafe-coerce": ">=6.0.0 <7.0.0",
"untagged-union": ">=1.0.0 <2.0.0",
"variant": ">=8.0.0 <9.0.0",
"variant-encodings": ">=2.0.0 <3.0.0"
}
}```
This version has already been published to the registry, but the docs have not been uploaded to Pursuit. Skipping registry publishing and retrying Pursuit publishing...
Could not publish your package to Pursuit because an error was encountered (cc: @purescript/packaging): Expected to receive a 201 status from Pursuit, but received 502 instead.
It's one of those mysterious packages again which does not want to find its way to Pursuit.
{ "name": "marked", "ref": "v0.1.1", "compiler": "0.15.10", "location": { "githubOwner": "thought2", "githubRepo": "purescript-marked" } }
Package source does not have a purs.json file, creating one from your spago.yaml file...
Converted your spago.yaml into a purs.json manifest to use for publishing:
"name": "marked",
"version": "0.1.0",
"license": "BSD-3-Clause",
"location": {
"githubOwner": "thought2",
"githubRepo": "purescript-marked"
},
"dependencies": {
"dts": ">=1.0.0 <2.0.0",
"either": ">=6.1.0 <7.0.0",
"foreign-object": ">=4.1.0 <5.0.0",
"integers": ">=6.0.0 <7.0.0",
"labeled-data": ">=0.2.0 <0.3.0",
"literals": ">=1.0.2 <2.0.0",
"maybe": ">=6.0.0 <7.0.0",
"newtype": ">=5.0.0 <6.0.0",
"nullable": ">=6.0.0 <7.0.0",
"prelude": ">=6.0.1 <7.0.0",
"ts-bridge": ">=4.0.0 <5.0.0",
"unsafe-coerce": ">=6.0.0 <7.0.0",
"untagged-union": ">=1.0.0 <2.0.0",
"variant": ">=8.0.0 <9.0.0",
"variant-encodings": ">=2.0.0 <3.0.0"
}
}```
This version has already been published to the registry, but the docs have not been uploaded to Pursuit. Skipping registry publishing and retrying Pursuit publishing...
Successfully uploaded package docs to Pursuit! 🎉 🚀