Add github repo, since publishing without it seems to not work

parent 08539d41
...@@ -3,6 +3,6 @@ ...@@ -3,6 +3,6 @@
"devDependencies": { "devDependencies": {
"purescript": "0.15.15", "purescript": "0.15.15",
"purs": "^0.3.0", "purs": "^0.3.0",
"spago": "next" "spago": "0.93.29"
} }
} }
\ No newline at end of file
...@@ -3,7 +3,7 @@ workspace: ...@@ -3,7 +3,7 @@ workspace:
address-rfc2821: address-rfc2821:
path: ./ path: ./
dependencies: dependencies:
- either - either: ">=6.1.0 <7.0.0"
- ffi-simple: ">=0.5.1 <0.6.0" - ffi-simple: ">=0.5.1 <0.6.0"
- prelude: ">=6.0.1 <7.0.0" - prelude: ">=6.0.1 <7.0.0"
test_dependencies: test_dependencies:
......
...@@ -37,8 +37,9 @@ package: ...@@ -37,8 +37,9 @@ package:
# https://github.com/purescript/registry-dev/blob/master/SPEC.md#33-manifest # https://github.com/purescript/registry-dev/blob/master/SPEC.md#33-manifest
exclude: exclude:
- "test/graphs/**/*" - "test/graphs/**/*"
# The place where the Registry will fetch the source from. # The place where the Registry will fetch the source from.
# This is optional since you might want to release the code without # This is optional since you might want to release the code without
# publishing to the Registry, which is what this is needed for. # publishing to the Registry, which is what this is needed for.
#location: location:
# url: https://gitlab.iscpif.fr/gargantext/purescript-address-rfc2821.git githubOwner: "garganscript"
githubRepo: "purescript-address-rfc2821"
...@@ -2,7 +2,7 @@ module Test.Data.RFC2821.Spec where ...@@ -2,7 +2,7 @@ module Test.Data.RFC2821.Spec where
import Data.Either (Either(..), isLeft, isRight) import Data.Either (Either(..), isLeft, isRight)
import Data.RFC2821 as RFC2821 import Data.RFC2821 as RFC2821
import Debug (spy) -- import Debug (spy)
import Prelude import Prelude
import Test.Spec (Spec, describe, it) import Test.Spec (Spec, describe, it)
import Test.Spec.Assertions (shouldEqual) import Test.Spec.Assertions (shouldEqual)
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment