Skip to content

The community needs a stronger WARNING about the change in private modules - proxy.golang.org #33980

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.

Sign up for GitHub

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

Jump to bottom
Closed
hammerandtongs opened this issue Aug 30, 2019 · 2 comments
Closed

The community needs a stronger WARNING about the change in private modules - proxy.golang.org #33980

hammerandtongs opened this issue Aug 30, 2019 · 2 comments
Labels
FrozenDueToAge

Comments

@hammerandtongs
Copy link

https://tip.golang.org/cmd/go/#hdr-Module_configuration_for_non_public_modules

This was featured nowhere in the announcement -

https://blog.golang.org/module-mirror-launch

It would seem to impact a large number of people using golang.
@donatj
Copy link

donatj commented Aug 30, 2019

I would request you to be able to mark a module as private in the go.mod rather than depending on each machine setting it's environmental variables.

@katiehockman
Copy link
Contributor

katiehockman commented Aug 30, 2019 •
edited
Loading

Duplicate of #33796. It's in the first paragraph of the release notes and the first paragraph of the blog post

@donatj donatj mentioned this issue Aug 30, 2019
Closed
@golang golang locked and limited conversation to collaborators Aug 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@donatj @hammerandtongs @gopherbot @katiehockman