From 48920637eaa9f0e2be0ddac3d6277a8d39e9c07d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E8=83=A1=E7=8E=AE=E6=96=87?= Date: Wed, 11 Dec 2024 01:16:38 +0800 Subject: [PATCH] remove out-of-date comments about version mark_new_version.sh (actually mark-new-version.sh) has been removed. And we are not creating vX.Y tags. We are using ldflags -X now. Kubernetes-commit: 0f0f9d01c0db8906989616ccc1ef04175035ddf9 --- pkg/version/base.go | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/pkg/version/base.go b/pkg/version/base.go index 676d51d3..edfa5e04 100644 --- a/pkg/version/base.go +++ b/pkg/version/base.go @@ -24,15 +24,9 @@ package version // information from git. // // If you are looking at these fields in the git tree, they look -// strange. They are modified on the fly by the build process. The +// strange. They are set by the build process with ldflags -X. The // in-tree values are dummy values used for "git archive", which also // works for GitHub tar downloads. -// -// When releasing a new Kubernetes version, this file is updated by -// build/mark_new_version.sh to reflect the new version, and then a -// git annotated tag (using format vX.Y where X == Major version and Y -// == Minor version) is created to point to the commit that updates -// pkg/version/base.go var ( // TODO: Deprecate gitMajor and gitMinor, use only gitVersion // instead. First step in deprecation, keep the fields but make