Closed samuelventura closed 1 year ago
Hex shows different checksum.
Same problam, create "VERSION" file in /deps/castore/, and compile ok.
Yeah, I just did echo "0.1.21" > deps/catstore/VERSION
as a stopgap.
i already send a pull request and wait respon
Until the PR is merged and a new version is pushed to hex you can probably use
{:castore, "== 0.1.20", override: true}
in your deps to keep packages from updating castore to 0.1.21. This will work in your ci/cd pipelines where manually adding the file to the deps folder will not.
thanks, that's help a lot
Yeah, I just did
echo "0.1.21" > deps/catstore/VERSION
as a stopgap.
That should be echo "0.1.21" > deps/castore/VERSION
Hex shows different checksum.
- https://hex.pm/packages/castore/0.1.21
- 1e4c72e5c476e50deee88ec1e6949f804c9a410d813dc17d3ce78b9b7c55b289
Indeed, the GitHub tagged version does not require VERSION
, so it appears a different file was included in the hex package.
We have released 0.1.22 that matches what's on github.
mix.lock
mix.exs