Re: [go-nuts] How to prove that GOPROXY is being used?

you'll want to clear your module cache, and then watch go get / go mod download with -v (for downloading) and/or -x (see if it invoked git commands). - sean On Sat, Dec 14, 2024, 09:02 David Karr wrote: > I'm currently using Go 1.23.2. We have a few applications that reference > packages on gi

Re: [go-nuts] Removing a module from a multi-module repository

There's no automatic upgrade path, the best you can do is mark the sub module as retracted and/or Deprecated. your users will need some manual action to drop it as a dependency. - sean On Sat, Dec 14, 2024, 13:37 'Doug Fawley' via golang-nuts < golang-nuts@googlegroups.com> wrote: > The followin

[go-nuts] Removing a module from a multi-module repository

The following section indicates that it should be possible to safely remove a module from a multi-module repository, and move the removed module's packages to the parent module: https://go.dev/wiki/Modules#is-it-possible-to-remove-a-module-from-a-multi-module-repository However, it doesn't say

[go-nuts] How to prove that GOPROXY is being used?

I'm currently using Go 1.23.2. We have a few applications that reference packages on github. We're now in a situation where we have to ensure that packages are obtained from our internal github proxy, not directly from github. So, I set GOPROXY to point to the repository we set up for this, a

[go-nuts] Go 1.24 Release Candidate 1 is released

Hello gophers, We have just released go1.24rc1, a release candidate version of Go 1.24. It is cut from release-branch.go1.24 at the revision tagged go1.24rc1. Please try your production load tests and unit tests with the new version. Your help testing these pre-release versions is invaluable. Re