oltarasenko
I am having a bit strange issue with hex. I have pushed a new version of a package there: crawly | Hex
But when I am trying to get it, e.g.: GitHub - oltarasenko/crawly-cars · GitHub
I am getting:
➜ cars_shop git:(master) mix deps.get
** (Mix) No matching version for crawly ~> 0.2.0 (from: mix.exs) in registry
The latest version is: 0.1.0```
Also, it looks like hex knows the real information about the package:
cars_shop git:(master) mix hex.info crawly
high-level web crawling & scraping framework for Elixir.
Config: {:crawly, "~> 0.2.0"}
Releases: 0.2.0, 0.1.2, 0.1.1, 0.1.0
Licenses: Apache 2.0
Links:
Docs: https://oltarasenko.github.io/crawly/
GitHub: https://github.com/oltarasenko/crawly
At first, I thought it might be a caching issue. So I tried to remove the ~/.hex folder. But it did not help :(.
Could someone advise what is wrong?
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Producing high quality Elixir screencasts since 2017.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #phoenix_html
- #iex
- #graphql
- #ai
- #genstage
- #elixirconf-us
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Bringing learning, work and compliance together since 1987.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
First 2 of 2 Posts
axelson
Hmmm, sounds like it could be related to this thread Getting 502 from Hex.pm, when trying to publish a package
supersimple
yes, as @axelson said it is related to the other issue. There is an open issue on hexpm discussing the cause/solution https://github.com/hexpm/hexpm/issues/835