On Thu Jul 1, 2021 at 17:47 CET, Jay Conrod wrote:
> As Dan mentioned, the version containing the retractions must be the
> highest version, so you'd need to tag v1.4.3 or higher. If that version
> retracts itself, it won't appear in the version list either.
right.
indeed, after having tagged
As Dan mentioned, the version containing the retractions must be the
highest version, so you'd need to tag v1.4.3 or higher. If that version
retracts itself, it won't appear in the version list either.
On Thu, Jul 1, 2021 at 1:58 AM Sebastien Binet wrote:
> Hi Jay,
>
> On Thu Jul 1, 2021 at
Hi Jay,
On Thu Jul 1, 2021 at 00:45 CET, Jay Conrod wrote:
> Hi Sebastien, once a version is in proxy.golang.org, it usually can't be
> removed. This is important to ensure that builds continue working when a
> repository disappears upstream.
>
> You may want to publish a new version with a
On Wed, 2021-06-30 at 15:45 -0700, 'Jay Conrod' via golang-nuts wrote:
> Hi Sebastien, once a version is in proxy.golang.org, it usually can't
> be removed. This is important to ensure that builds continue working
> when a repository disappears upstream.
>
> You may want to publish a new version
Hi Sebastien, once a version is in proxy.golang.org, it usually can't be
removed. This is important to ensure that builds continue working when a
repository disappears upstream.
You may want to publish a new version with a retract directive in go.mod,
marking the earlier versions as invalid. In
hi there,
I've forked a fork of a Go package (github.com/jung-kurt/gofpdf).
But as the modus operandi of such a thing is rather unwieldy in github
(PRs would always be created by default against the original package
instead of my fork), I've deleted the forked repo, created a new repo
with the
