Was the 0.1.2 tag moved?

[cameracker]

I've been wrestling with install failures that suddenly happened seemingly out of nowhere.

Did the tag for 0.1.2 move?

go: downloading github.com/nats-io/nkeys v0.1.2
verifying github.com/nats-io/nkeys@v0.1.2: checksum mismatch
	downloaded: h1:6JJydNSjt/lqhfM+ngyaLk9Wa/d3UW/YyEqj8OrDV4w=
	go.sum:     h1:kWUa9fUdAOW426qaAD1V4+suF4On2eTr2n/FE/XSGpg=

If so, could there be a note added to the release notes that the tag was moved?

Thanks!

[kozlovic]

We are very sorry for the inconvenience. There was indeed a problem last week when a tag was created and there was a build problem. I believe that this release/tag was then removed and recreated. It could be that you happened to capture in your go.mod/sum the info of the tag that has since been replaced?

If you remove the entry from go.sum and try again, can you download ok? I just tried to update a project that used to reference 0.1.0 to 0.1.2 and it works fine.

I will add a note to the 0.1.2 release page for users that may experience the same issue. Again, sorry for the troubles.

[cameracker]

Hey no sweat, this stuff happens and I'm honestly a bit new to modules so this might just be a standard operating procedure thing I was missing.

We really appreciate the quick response. The remediation you recommended appears to have worked.

Have a great day <3

[kozlovic]

Thanks, I am going to update the release notes since it seem to have worked.

[jerome-laforge]

In my enterprise, we use internal go proxy from jfrog, I don't have the right to modify its cache.

Unfortunately, even if remove all the entries for nkeys in the go.sum from the project, that doesn't work:

verifying github.com/nats-io/nkeys@v0.1.2: checksum mismatch
        downloaded: h1:6JJydNSjt/lqhfM+ngyaLk9Wa/d3UW/YyEqj8OrDV4w=
        sum.golang.org: h1:kWUa9fUdAOW426qaAD1V4+suF4On2eTr2n/FE/XSGpg=

If I use official proxy from golang and I remove all entries in the go.sum from the project that works.

Unfortunately our CI uses our internal go proxy (and not official one), so our CI is stuck.

Is it possible for you to release a new tag 0.1.3 in order to fix it.

Many thx.

[kozlovic]

@jerome-laforge I will release a new tag today. We are very sorry for the inconvenience.

[jerome-laforge]

many thx @kozlovic

[kozlovic]

@jerome-laforge @CameronAckermanSEL I have just release v0.1.3. Hopefully that solves the problem. Let me know if that is the case.

[cameracker]

Thank you very much :)

[jerome-laforge]

@kozlovic it works like a charm.
Many thanks.