-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tags were moved, but not published #40
Comments
@ryan-haskell pls republish package as 2.3.1. Your readme update changed hash |
If possible, moving the tag back to "repair" 2.3.0 would be even better I'd say. |
find replace
|
also still breaks because it imported |
apparently in my case (after checking with proper tool: elm-json caused by elm-visualization that still depend on old at least this is temporary solution until all dependencies updated |
We also are seeing the issue:
|
Any update on resolving this? |
+1 for this issue |
I used |
The line in my elm.json now looks like this: |
Resolves issue with mismtached tag hash: ryan-haskell/date-format#40 (comment)
Hi all, happy to help with this issue- but I'm not sure exactly how to implement the suggestions here. This is the first time I've messed with my username and tags for an Elm package, so your guidance would be appreciated! For solutions involving tagging, could you walk me through the git commands and elm publish commands you are hoping I can run? For folks that are blocked on this, my package consists of three Elm files, and I think the easiest solution is to move them into your codebase. I'm sure many of you have done this, but for anyone who are feeling stuck in the interim- this code is open source and free to steal! It only depends on Sorry for the inconvenience, I expected republishing my package would "just work" for folks- I didn't anticipate people to have issues with the old tags (or it somehow depending on an old version of itself!) Any help would be appreciated, thank you all! |
Hi. Please let me share my concern: |
Ahh, I see! This is from another Elm package that depends on mine. Tereza was able to release a new version of Elm Charts with the updated dependency last week: —- Still open to concrete steps I can take on my end, in case folks are able to provide specific git / elm publish commands |
Hello Ryan, thanks a lot for your answer, this solved my issue. Thanks ! |
I also ran into this issue, because I'm using I had to remove all of the following packages from the
|
Hi @ryan-haskell , just want to let you know that the issue is also on elm-transformer. Thanks `@parcel/elm-transformer: I downloaded the source code for ryannhg/date-format 2.3.0 from:
But it looks like the hash of the archive has changed since publication: Expected: 70c67866fed499bec685f43f23fea279556757f2 This usually means that the package author moved the version tag, so report it |
Hi, I upgraded my elm.json and got But now I get a similar one on:
When I look at https://github.com/ryan-haskell/elm-spa I see that the last release is Replacing |
https://github.com/dillonkearns/elm-rss also depends on this package through https://github.com/dmy/elm-imf-date-time |
Seems unused in current version and caused issues (ryan-haskell/date-format#40 (comment))
I started to get complilation error: Same for 2.2.0 and 2.3.0
I downloaded the source code for ryannhg/date-format 2.3.0 from:
But it looks like the hash of the archive has changed since publication:
Expected: 70c67866fed499bec685f43f23fea279556757f2
Actual: 86534146f5a550bb8e87b87a7484ea5732090bb5
The text was updated successfully, but these errors were encountered: