Release new version? #6
Labels
No Label
kind/breaking
kind/bug
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/security
kind/testing
kind/translation
kind/ui
lgtm/done
lgtm/need
lgtm/need
priority/critical
priority/low
priority/maybe
priority/medium
refactor
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
status/blocked
status/needs-feedback
status/wip
No Milestone
No Assignees
3 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: macaron/macaron#6
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
cc: @lunny @zeripath @techknowlogick
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 .
depend on #7
Since #7 merged, we can tag the version.
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.And maybe we should wait #1 and #5
I've just tagged 1.4.0, and so I will close this.