Skip to content
Browse files

New release of odo! 1.0.1 (#2373)

**What kind of PR is this?**
DELETE the kind(s) which are not applicable before opening the PR.

/kind feature

**What does does this PR do / why we need it**:

New version of odo (1.0.1)

**Which issue(s) this PR fixes**:


**How to test changes / Special notes to the reviewer**:


Signed-off-by: Charlie Drage <>
  • Loading branch information...
cdrage committed Nov 7, 2019
1 parent c281978 commit a95bd7bb496f96ce39719c71584988ccbd215646
Showing with 4 additions and 4 deletions.
  1. +1 −1 Dockerfile.rhel
  2. +1 −1 pkg/version/version.go
  3. +1 −1 scripts/
  4. +1 −1 scripts/
@@ -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=1.0.0
LABEL version=1.0.1

COPY --from=builder /go/src/ /usr/share/openshift/odo/mac/odo
COPY --from=builder /go/src/ /usr/share/openshift/odo/windows/odo.exe
@@ -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 = "v1.0.0"
VERSION = "v1.0.1"

// 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$(GITCOMMIT)"
@@ -7,7 +7,7 @@ set -e

# Latest released odo version

@@ -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:=1.0.0}
export ODO_VERSION=${ODO_VERSION:=1.0.1}

export GIT_COMMIT=${GIT_COMMIT:=`git rev-parse --short HEAD 2>/dev/null`}

0 comments on commit a95bd7b

Please sign in to comment.
You can’t perform that action at this time.