Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please tag new release -- post rename #39

Closed
tep opened this issue Sep 20, 2019 · 1 comment
Closed

Please tag new release -- post rename #39

tep opened this issue Sep 20, 2019 · 1 comment

Comments

@tep
Copy link

tep commented Sep 20, 2019

I'm forgoing your issue template since it's format is orthogonal to the issue at hand.

The latest tagged release (v0.2.2) is from 25 Jan 2018 -- back when the package was still named memmap. This is what gets downloaded by go get when using a modern (i.e. module-aware) version of Go.

Therefore, if I import "github.com/bradleyjkemp/memviz" into a project that uses modules, I'm compelled to reference it as package memmap... and this acutely unballances my already precarious feng shui.

Please tag a new release where the package name and the repo's basename agree.

Thankyouverymuchandhaveaniceday.

@bradleyjkemp
Copy link
Owner

Wow yeah that's a big oversight 🤦‍♂Just tagged the current master as v0.2.3 which should fix the issue. Thanks for raising this! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants