Closed migueleliasweb closed 1 year ago
cc @vburenin
bump this
@kazhuravlev I see you're the last committer on this, would this be possible? We have tooling that can't install off of branch/sha so need a release tag to work off of.
@vancluever I am not a maintainer/owner. I cannot do anything (only create a fork and support it in my repo?). This tool is looks like abandoned.
Anyway, in case that you want to use the latest changes from master
- you can do it without tags like
go install github.com/vburenin/ifacemaker@187c3829a589ed2a580731a000f7a4f61cc01e80
where 187c3829a589ed2a580731a000f7a4f61cc01e80
is a hash of commit in this repo
it is not really abandoned, it simply works without changes where it supposed to. however, I haven't tested it with generics.
Indeed it does work and we are using it :) Thanks for cutting the release @vburenin!
You are welcome. I haven't build binaries though. Travis CI is asking for $ due to too many users. On my end it is always built from sources, releases are kinda not necessary.
@vburenin yeah go install
works for us, we just need a semver refereanceable. Thanks again!
@vburenin looks like the release was created against an old commit and does not include recent changes like #52 which we need. Can you tag another release quick?
hm...
I had to remove remote tag first before pushing it... uh oh
@vburenin the module proxy probably has a bad cached version now, you might need to correct that by pushing a new tag and retracting v1.2.0. The module proxy landing page has a section on that (see https://proxy.golang.org/, "I removed a bad release from my repository but it still appears in the mirror, what should I do?").
republished it as v1.2.1, hopefully it works.
@vburenin looking good now, thanks for your help!
The latest available release doesn't seem to be up-to-date with the latest changes in the codebase.
Should a new one be created?