-
Notifications
You must be signed in to change notification settings - Fork 277
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
JAR checksum of Maven artifact doesn't match GitHub release #6837
Comments
This is probably related to #6651 . I believe the sonatype release process itself rebuilds the jar which leads to the difference. I'll investigate on Monday |
Hey @randomanderson, any results from your investigation? |
@der-eismann That PR highlighted a much bigger issue. Different jobs are rebuilding the jar instead of reusing previously built artifacts. That includes more than just maven vs github release artifacts. For example, kubernetes lib injection images, circleci, etc all have different checksums. I'm currently working on a larger fix for all of it. |
This PR #6939 from @randomanderson should address the issue. |
We noticed this while updating our local java environment. Is there a specific reason for this? Previously this was never an issue and paranoid minds would think of manipulation here.
The text was updated successfully, but these errors were encountered: