Bump odo to 2.4.3 (#5261)

This commit is contained in:
Dharmit Shah
2021-11-30 13:10:22 +05:30
committed by GitHub
parent d72d0c6603
commit 16dd43ce19
3 changed files with 3 additions and 3 deletions

View File

@@ -16,7 +16,7 @@ LABEL com.redhat.component=atomic-openshift-odo-cli-artifacts-container \
summary="This image contains the Linux, Mac and Windows version of odo"
# Change version as needed. Note no "-" is allowed
LABEL version=2.4.2
LABEL version=2.4.3
COPY --from=builder /go/src/github.com/openshift/odo/dist/bin/darwin-amd64/odo /usr/share/openshift/odo/mac/odo
COPY --from=builder /go/src/github.com/openshift/odo/dist/bin/windows-amd64/odo.exe /usr/share/openshift/odo/windows/odo.exe

View File

@@ -12,7 +12,7 @@ Changing these values will change the versioning information when releasing odo.
var (
// VERSION is version number that will be displayed when running ./odo version
VERSION = "v2.4.2"
VERSION = "v2.4.3"
// GITCOMMIT is hash of the commit that will be displayed when running ./odo version
// this will be overwritten when running build like this: go build -ldflags="-X github.com/openshift/odo/cmd.GITCOMMIT=$(GITCOMMIT)"

View File

@@ -5,7 +5,7 @@ set +ex
echo "Reading ODO_VERSION, ODO_RELEASE and GIT_COMMIT env, if they are set"
# Change version as needed. In most cases ODO_RELEASE would not be touched unless
# we want to do a re-lease of same version as we are not backporting
export ODO_VERSION=${ODO_VERSION:=2.4.2}
export ODO_VERSION=${ODO_VERSION:=2.4.3}
export ODO_RELEASE=${ODO_RELEASE:=1}
export GIT_COMMIT=${GIT_COMMIT:=`git rev-parse --short HEAD 2>/dev/null`}