Skip to content

Commit

Permalink
Include version to binaries of each release (#32)
Browse files Browse the repository at this point in the history
* Add release version to release.yaml

Signed-off-by: thepetk <thepetk@gmail.com>

* Update readme.md

Signed-off-by: thepetk <thepetk@gmail.com>

* Add .exe extension for windows architecture

Signed-off-by: thepetk <thepetk@gmail.com>

---------

Signed-off-by: thepetk <thepetk@gmail.com>
  • Loading branch information
thepetk authored Oct 10, 2023
1 parent 6b0b633 commit 83ea268
Show file tree
Hide file tree
Showing 2 changed files with 8 additions and 2 deletions.
8 changes: 7 additions & 1 deletion .github/workflows/release.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,13 @@ jobs:
GOOSARCH=${{matrix.goosarch}}
GOOS=${GOOSARCH%/*}
GOARCH=${GOOSARCH#*/}
BINARY_NAME=alizer-$GOOS-$GOARCH
RELEASE_VERSION=${GITHUB_REF#refs/*/}
if [ "$GOOS" == "windows" ]
then
BINARY_NAME=alizer-$RELEASE_VERSION-$GOOS-$GOARCH.exe
else
BINARY_NAME=alizer-$RELEASE_VERSION-$GOOS-$GOARCH
fi
echo "BINARY_NAME=$BINARY_NAME" >> $GITHUB_ENV
echo "GOOS=$GOOS" >> $GITHUB_ENV
echo "GOARCH=$GOARCH" >> $GITHUB_ENV
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -194,7 +194,7 @@ For each release a group of binary files is generated. More detailed we have the
In order to download a binary file:
* Go to the release you are interested for `https://github.com/devfile/alizer/releases/tag/<release-tag>`
* In the **Assets** section you will see the list of generated binaries for the release.
* In the **Assets** section you will see the list of generated binaries for the release. The names of the binaries are following the template `alizer-{version}-{ostype}-{architecture}`.
## Feedback & Questions
Expand Down

0 comments on commit 83ea268

Please sign in to comment.