Nancy will be moving to 1.0.0 soon and have new usage #1320
Labels
Comments
|
Hey, thank you for opening your first Issue ! 🙂 If you would like to contribute we have a guide for contributors. |
|
THANK YOU BORING CYBORG! |
|
@DarthHater thanks for the heads up 💯 PS: The bot is funny right 😆 |
sayboras
added a commit
to sayboras/golangci-lint
that referenced
this issue
Aug 18, 2020
This is suggested by nancy team to avoid coming breaking change Relates: golangci#1320
sayboras
added a commit
that referenced
this issue
Aug 19, 2020
This is suggested by nancy team to avoid coming breaking change Relates: #1320
|
Pending task is to make sure nancy v1.0 will not break once it's realease. |
sayboras
added
good first issue
sayboras
added a commit
to sayboras/golangci-lint
that referenced
this issue
Oct 3, 2020
This commit is to update version to 1.0.1 Closes golangci#1320 Signed-off-by: Tam Mach <[email protected]>
sayboras
added a commit
that referenced
this issue
Oct 3, 2020
This commit is to update version to 1.0.1 Closes #1320 Signed-off-by: Tam Mach <[email protected]>
ldez
removed
help wanted
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello!
We saw you are using
nancy, and we are humbled! I thought I'd reach out and let you know that we will have a 1.0.0 release coming soon, and usage is going to change slightly. To avoid disruption to your project, rather than usinglateston your Docker image tag, I'd suggest usingv0.3orv0for now, and then moving back tolatestonce you've had some time to digest the changes. I'd say we are about a week out from merging those changes, hence the heads up! They aren't gigantic, but we've moved some of the functionality into anancy sleuthcommand.CC @zendern @bhamail
The text was updated successfully, but these errors were encountered: