-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
Add back go module files to release-3.3 branch #12233
Comments
OK, I see ,thank you.Do I need to do it? |
@cfc4n Yeah that would be great if you can help... Or do you still need module files? I haven't figured out how go module files were affecting version strings... |
I think , most user need module files who troubled by this problem. ref #12068 Can you give some message about release errors? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
c3780bb
@cfc4n Had to revert this commit in release-3.3 branch because our release script was overwriting the version name string from this go.mod file.
The text was updated successfully, but these errors were encountered: