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

chore: use retract to try to invalidate the v1.0.0 #26

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

ccoVeille
Copy link
Owner

This version was not ready for production, but was published without prerelease flag

Fixes #24

More information about retract in the go.mod documentation
https://go.dev/ref/mod#go-mod-file-retract

This version was not ready for production, but was published without prerelease flag

Fixes #24

More information about retract in the go.mod documentation
https://go.dev/ref/mod#go-mod-file-retract
Copy link

codecov bot commented Sep 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (3049cd5) to head (9fb455f).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #26   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           60        60           
=========================================
  Hits            60        60           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@ldemailly
Copy link
Collaborator

if I recall that will only take effect after you push a (newer I think, server wise) tag

alternative is you move it to different org or rename it and abandon this location :)

@ccoVeille
Copy link
Owner Author

Exactly, the effext might be visible after the next release

@ccoVeille ccoVeille merged commit ddf82b9 into main Sep 9, 2024
5 checks passed
@ccoVeille ccoVeille deleted the prerelease-fix branch September 9, 2024 19:05
@ldemailly
Copy link
Collaborator

It worked!

Screenshot 2024-09-09 at 3 36 07 PM

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.

Try to mitigate v1.0.0 release
2 participants