go-jira icon indicating copy to clipboard operation
go-jira copied to clipboard

v1.12.0 checksum mismatch

Open Jonnymcc opened this issue 3 years ago • 1 comments

Describe the bug

Dependabot reports a checksum mismatch between what is downloaded and what is in go.sum.

Dependabot encountered the following error:

verifying github.com/andygrunwald/[email protected]: checksum mismatch
	downloaded: h1:lf2Y3VFMuYNPbgAiLBHVDXYbmXrA4+/++7D6EFHK7xk=
	go.sum:     h1:JJi2cEDmDxVtTXxC8ruLDbtOU6pA4OLeL0niyfNcoWw=

To Reproduce

Expected behavior

The downloaded checksum should match what we had in go.sum.

Possible Solution

Your Environment

Include as many relevant details about the environment you experienced the problem in

  • go-jira version (git tag or sha): v1.12.0
  • Go version (go version): go version go1.14.2 darwin/amd64
  • Jira version:
  • Jira type (cloud or on-premise): Cloud
  • Involved Jira plugins:
  • Operating System and version: MacOS Big Sur 11.2.3 (20D91)

Additional context

When I run go build locally the same old checksum (JJi2) appears, but dependabot consistently shows the same differing checksum (lf2Y). Which one should I expect?

Jonnymcc avatar Mar 26 '21 16:03 Jonnymcc

Hi! Thank you for taking the time to create your first issue! Really cool to see you here for the first time. Please give us a bit of time to review it.

github-actions[bot] avatar Mar 26 '21 16:03 github-actions[bot]

Hey,

I am very sorry that this issue has been open for a long time with no final solution. We work on this project in our spare time, and sometimes, other priorities take over. This is the typical open source dilemma.

However, there is news: We are kicking off v2 of this library 🚀

To provide visibility, we created the Road to v2 Milestone and calling for your feedback in https://github.com/andygrunwald/go-jira/issues/489

The development will take some time; however, I hope you can benefit from the changes. If you seek priority development for your issue + you like to sponsor it, please contact me.

What does this mean for my issue?

We will work on this issue indirectly. This means that during the development phase, we aim to tackle it. Maybe in a different way like it is currently handled. Please understand that this will take a while because we are running this in our spare time.

Final words

Thanks for using this library. If there is anything else you would like to tell us, let us know!

andygrunwald avatar Aug 21 '22 14:08 andygrunwald