You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/917-go-modules/README.md#publish-staging-component-modules-to-individual-repositories:
> Generate synthetic Godeps.json files containing the SHA or git tag of
> module dependencies, for consumption by downstream consumers using
> dependency management tools like glide. Continue publishing these at
> least until our minimum supported version of go defaults to enabling
> module support (currently targeted for go 1.13, which is approximately
> Kubernetes 1.16-1.17 timeframe).
Now that Go 1.16 is in module-aware mode by default, it should be safe
to remove support for publishing synthetic `Godeps.json` files.
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ The publishing bot publishes the code in `k8s.io/kubernetes/staging` to their ow
10
10
11
11
It pulls the latest k8s.io/kubernetes changes and runs `git filter-branch` to distill the commits that affect a staging repo. Then it cherry-picks merged PRs with their feature branch commits to the target repo. It records the SHA1 of the last cherrypicked commits in `Kubernetes-sha: <sha>` lines in the commit messages.
12
12
13
-
The robot is also responsible to update the `go-mod` and the `vendor/` directory for the target repos, and to create a fake (sparse and repo level based) `Godeps/Godeps.json`.
13
+
The robot is also responsible to update the `go-mod` and the `vendor/` directory for the target repos.
0 commit comments