Skip to content
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

retract v1.1.0 #1022

Merged
merged 1 commit into from
Jan 21, 2025
Merged

retract v1.1.0 #1022

merged 1 commit into from
Jan 21, 2025

Conversation

jmank88
Copy link
Contributor

@jmank88 jmank88 commented Jan 21, 2025

When the tooling attempts to use v1.1.0, a checksum mismatch is often encountered. The tag must have been moved after publishing and being cached in the sumdb. Using newer versions does not prevent encountering this problematic version. It must be retracted: https://go.dev/ref/mod#go-mod-file-retract

We will have to publish a new version in order for the tooling to recognize this retraction.

@cl-sonarqube-production
Copy link

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

@aalu1418 aalu1418 enabled auto-merge (squash) January 21, 2025 21:08
@aalu1418 aalu1418 merged commit 3423966 into develop Jan 21, 2025
36 checks passed
@aalu1418 aalu1418 deleted the retract-v1.1.0 branch January 21, 2025 21:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants