Release new version? #6

Closed
opened 2019-08-03 16:53:50 +00:00 by tamalsaha · 7 comments
Contributor

Should a new version, say v1.4.0 be released with updated module path and any fixes?

I think then it should be vendored in all the other repos.

Should a new version, say v1.4.0 be released with updated module path and any fixes? I think then it should be vendored in all the other repos.
Author
Contributor
cc: @lunny @zeripath @techknowlogick
Contributor

I think we have to wait macaron/inject#1. There is still a wrong dependent package, see https://gitea.com/macaron/macaron/src/branch/master/go.mod#L8 .

I think we have to wait https://gitea.com/macaron/inject/pulls/1. There is still a wrong dependent package, see https://gitea.com/macaron/macaron/src/branch/master/go.mod#L8 .
Contributor

depend on #7

depend on https://gitea.com/macaron/macaron/pulls/7
Contributor

Since #7 merged, we can tag the version.

Since #7 merged, we can tag the version.
Author
Contributor

In the same vein, should a v0.1.0 release be cut for all the other repos? I think it will make it far more readable in a go.mod file.

In the same vein, should a `v0.1.0` release be cut for all the other repos? I think it will make it far more readable in a go.mod file.
Contributor

And maybe we should wait #1 and #5

And maybe we should wait #1 and #5
Contributor

I've just tagged 1.4.0, and so I will close this.

I've just tagged 1.4.0, and so I will close this.
This repo is archived. You cannot comment on issues.
No description provided.