Re-releasing packages with different github usernames (and not v1.0.0) breaks package download endpoints

[jxlxx]

Quick Summary: Skinney/murmur3 v2.0.8 has been re-released as robinheghan/murmur3 v1.0.0, and now anything using the Skinney version breaks (because GitHub tracks username changes, but their versions are different).

Full Explanation:

• Skinney/murmur3 v2.0.8 is listed in elm packages here: https://package.elm-lang.org/packages/Skinney/murmur3/latest/
• GitHub automatically redirects to robinheghan/murmur3@2.0.8
• robinheghan/murmur3@2.0.8 does not exist
• (because the elm package manager required robinheghan/murmur3 to be released at 1.0.0)
• always breaks

SSCCE

elm install Skinney/murmur3

• Elm: 0.19.1
• Browser: n/a
• Operating System: NixOS 22.05 (Quokka)

Additional Details

Some context for the re-release: robinheghan/murmur3@ec218ce

Would just releasing robinheghan/murmur3@1.0.0 at v2.0.8? I think so. But I also think this might be a recurring issue (anytime someone changes their GitHub name for a package that isn't version 1.0.0).

CLI output:

$ elm install Skinney/murmur3
Here is my plan:

  Add:
    Skinney/murmur3    2.0.8

Would you like me to update your elm.json accordingly? [Y/n]: Y
-- PROBLEM DOWNLOADING PACKAGE -------------------------------------------------

I was trying to download the source code for Skinney/murmur3 2.0.8, so I tried
to fetch:

    https://github.com/Skinney/murmur3/zipball/2.0.8/

But it came back as 404 Not Found

This may mean some online endpoint changed in an unexpected way, so if does not
seem like something on your side is causing this (e.g. firewall) please report
this to https://github.com/elm/compiler/issues with your operating system, Elm
version, the command you ran, the terminal output, and any additional
information that can help others reproduce the error!

[github-actions]

Thanks for reporting this! To set expectations:

• Issues are reviewed in batches, so it can take some time to get a response.
• Ask questions in a community forum. You will get an answer quicker that way!
• If you experience something similar, open a new issue. We like duplicates.

Finally, please be patient with the core team. They are trying their best with limited resources.