Version downgrading broke some builds

[folex]

Hi! Thanks a lot for your hard work and contribution to the Elm ecosystem.

Renaming the version from 1.1.1 to 1.0.1 seems to broke some of my builds. It is possible that I'm not the only one. Could you please consider keeping 1.1.1 and keep the Elm ecosystem a little bit more stable?

Thanks in advance!

[chelovek0v]

Hi! I didn't rename the version, but I did rename my GH account and this broke things; I'm sorry and I didn't want this to happen. I sent emails to people who depend on my package advising them to update and notice the change.

Due to some limitations in Elm and GH I can't update or support the previous package(with the previous name and the version).

Your builds of course didn't break just because the version is changed, but because hashes of releases changed since I changed my account name. So the package is corrupted and elm spits errors at you. Fixing just a version won't do anything – you should update your dependencies with the new one.

"chelovek0v/bbase64": "1.0.1 <= v < 2.0.0" in your elm.json

Also you can read about a similar problem and how to protect from it https://discourse.elm-lang.org/t/skinney-murmur3-not-downloading/6285/3

[folex]

To me, it seemed like redirects worked fine, i.e., from the previous repo name to the current one, but then it failed because it got 404. Maybe if it weren't to 404, it would fail later due to hashing, as you say.

The log was like this

-- PROBLEM DOWNLOADING PACKAGE -------------------------------------------------

I was trying to download the source code for ivadzy/bbase64 1.1.1, so I tried to
fetch:

    https://github.com/ivadzy/bbase64/zipball/1.1.1/

But it came back as 404 Not Found.

It was easy to fix, however.

Thanks for your quick and kind reply!