Set module version to v1 #319
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
feedmeapples
commented
Oct 17, 2022
| // Completed - green | ||
| // Started - blue | ||
| // Others - default (white/black) | ||
| // |
There was a problem hiding this comment.
this extra line is now added by Go plugin automatically
|
Is this some kind of breaking change? |
as it was broken with |
alexshtin
approved these changes
Oct 20, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was changed
Set the mod version to v1
Why?
As we are not currently releasing v2 the mod version conflicts with the github release version, resulting in not being able to import the module in other projects
Checklist
Closes
How was this tested:
unit tests