You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there! First - thanks so much for Cobra, it's great!
I ran into a small issue with using Cobra and dep recently, centered around the current 0.0.2 tag and it's being out of date with the latest in master.
When running dep init on a repo that uses Cobra, the following constraint gets added to the Gopkg.toml file:
[[constraint]]
name = "github.com/spf13/cobra"
version = "0.0.2"
That tag points to this commit a1f051b, however I'm using the FParseErrWhitelist property of the cobra.Command struct, which wasn't added until #662
I've gotten around this in dep by updating the constraint to point at the latest revision like so (I could also point it at the master branch, assumedly):
[[constraint]]
name = "github.com/spf13/cobra"
revision = "615425954c3b0d9485a7027d4d451fdcdfdee84e"
but was wondering if we could get a 0.0.3 tag added that includes all of the latest commits?
The text was updated successfully, but these errors were encountered:
Hey there! First - thanks so much for Cobra, it's great!
I ran into a small issue with using Cobra and
dep
recently, centered around the current0.0.2
tag and it's being out of date with the latest inmaster
.When running
dep init
on a repo that uses Cobra, the following constraint gets added to theGopkg.toml
file:That tag points to this commit a1f051b, however I'm using the
FParseErrWhitelist
property of thecobra.Command
struct, which wasn't added until #662I've gotten around this in
dep
by updating the constraint to point at the latest revision like so (I could also point it at themaster
branch, assumedly):but was wondering if we could get a
0.0.3
tag added that includes all of the latest commits?The text was updated successfully, but these errors were encountered: