version tag
jdupl123 opened this issue · comments
Because there is no version tag go mod takes the last commit from master.
This caused our ci pipeline to break with the following error
/root/go/src/github.com/contribsys/faktory_worker_go/runner.go:289:9: undefined: client.Batch
After commit: f4d3451
Would it make sense to create version tags?
If anyone else has this issue you can put github.com/contribsys/faktory_worker_go v0.0.0-20191008193933-9f13abade33b in go.mod to get the stable version.
Sorry, I've both fixed that commit and introduced a v0.8.0 tag for the
previously stable code, before the recent work.
…On Tue, Dec 3, 2019 at 8:00 PM jdupl123 ***@***.***> wrote:
Because there is no version tag go mod takes the last commit from master.
This caused our ci pipeline to break with the following error
/root/go/src/github.com/contribsys/faktory_worker_go/runner.go:289:9:
undefined: client.Batch
After commit: f4d3451
<f4d3451>
Would it make sense to create version tags?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#31?email_source=notifications&email_token=AAAAWX6V7PHAYL7MQFACGEDQW4TOZA5CNFSM4JVCRUQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H54J7ZQ>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAWX5ONTNKYDSVIL3TNATQW4TOZANCNFSM4JVCRUQQ>
.
Great thanks.