Skip to content

Include version to binaries of each release#32

Merged
thepetk merged 3 commits intodevfile:mainfrom
thepetk:main
Oct 10, 2023
Merged

Include version to binaries of each release#32
thepetk merged 3 commits intodevfile:mainfrom
thepetk:main

Conversation

@thepetk
Copy link
Contributor

@thepetk thepetk commented Oct 9, 2023

What does this PR do?

This PR adds a the version of every release into each binary name generated from release.yaml.

Which issue(s) does this PR fix

fixes devfile/api#1212

PR acceptance criteria

Testing and documentation do not need to be complete in order for this PR to be approved. We just need to ensure tracking issues are opened.

  • Unit/Functional tests

  • Documentation

How to test changes / Special notes to the reviewer

An example run of the updated action can be found here: https://github.com/thepetk/devfile-alizer/releases/tag/v1.1.0

@thepetk thepetk self-assigned this Oct 9, 2023
@openshift-ci openshift-ci bot added the approved label Oct 9, 2023
@codecov
Copy link

codecov bot commented Oct 9, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (6b0b633) 70.49% compared to head (817c917) 70.49%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #32   +/-   ##
=======================================
  Coverage   70.49%   70.49%           
=======================================
  Files          11       11           
  Lines        1566     1566           
=======================================
  Hits         1104     1104           
  Misses        395      395           
  Partials       67       67           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Signed-off-by: thepetk <[email protected]>
Copy link
Member

@rm3l rm3l left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, but while you're at it, I was wondering if you could also add a .exe extension to the Windows binary? Otherwise, as I just tried it on Windows 11, the file looks suspicious when downloaded by the browser and does not appear as executable by default.
(But this can be handled in a separate issue if you prefer).

@thepetk
Copy link
Contributor Author

thepetk commented Oct 10, 2023

LGTM, but while you're at it, I was wondering if you could also add a .exe extension to the Windows binary? Otherwise, as I just tried it on Windows 11, the file looks suspicious when downloaded by the browser and does not appear as executable by default. (But this can be handled in a separate issue if you prefer).

Nice catch! I've added a commit to add the ".exe" extension for the windows binary. An example can be found here: https://github.com/thepetk/devfile-alizer/releases/tag/v1.1.1

@thepetk thepetk requested a review from rm3l October 10, 2023 10:26
@openshift-ci
Copy link

openshift-ci bot commented Oct 10, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l, thepetk

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@thepetk thepetk merged commit 83ea268 into devfile:main Oct 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add Alizer version to release binaries name

2 participants