Releases seems to be broken #39
Description
Hi Ryan, I'm not sure how, but the latest changes to your repo seem to have broken the releases.
Our CI started failing around when you made your last commit. It appears to fail when we're running some elm tooling.
Relevant logs:
Failing running elm-test-rs
elm-test-rs --fuzz 10
-- CORRUPT PACKAGE DATA --------------------------------------------------------
I downloaded the source code for ryannhg/date-format 2.3.0 from:
https://github.com/ryannhg/date-format/zipball/2.3.0/
But it looks like the hash of the archive has changed since publication:
Expected: 70c67866fed499bec685f43f23fea279556757f2
Actual: 86534146f5a550bb8e87b87a7484ea5732090bb5
This usually means that the package author moved the version tag, so report it
to them and see if that is the issue. Folks on Elm slack can probably help as
well.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Failing during elm-graphql
$ elm-graphql --schema-file ../hasura/schema.gql --output src/elm/ --base Builder --scalar-codecs CustomScalarCodecs && git apply patches/hasura-branch-main.patch
Generating files...
Command failed: elm make src/elm/Builder/VerifyScalarCodecs.elm --output=/dev/null
-- CORRUPT PACKAGE DATA --------------------------------------------------------
I downloaded the source code for ryannhg/date-format 2.3.0 from:
https://github.com/ryannhg/date-format/zipball/2.3.0/
But it looks like the hash of the archive has changed since publication:
Expected: 70c67866fed499bec685f43f23fea279556757f2
Actual: 86534146f5a550bb8e87b87a7484ea5732090bb5
This usually means that the package author moved the version tag, so report it
to them and see if that is the issue. Folks on Elm slack can probably help as
well.
--------------------------------------------
INVALID SCALAR DECODERS FILE
--------------------------------------------
Your custom scalar decoders module, `CustomScalarCodecs`, is invalid.
This is because either:
1) This is the first time you've run this CLI with the `--scalar-codecs` option.
In this case, get a valid file, you can start by copy-pasting `Builder.ScalarCodecs`. Then change the module name to `CustomScalarCodecs`
and you have a valid starting point!
2) You added or renamed a Custom Scalar in your GraphQL schema.
To handle the new Custom Scalar, you can copy the relevant entries from `CustomScalarCodecs`.
Check the following:
* You have a module called `CustomScalarCodecs`
* The module is somewhere in your elm path (check the `source-directories` in your `elm.json`)
You must:
* Have a type for every custom scalar
* Expose each of these types
* Expose a `codecs` value
Above the dashes (----) there are some details that might help you debug the issue. Remember, you can always
copy-paste the `Builder.ScalarCodecs` module to get a valid file.
After you've copy pasted the template file, or tried fixing the file,
re-run this CLI command to make sure it is valid.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.