Skip to content

Conversation

@ikalnytskyi
Copy link
Member

  1. Use setup-node@v2 instead of setup-node@v1. We don't use any
    specific, but let's stick with newer version assuming it's there
    for a greater good.

  2. Fix name of the uploaded release bundle. Apparently,
    ${{ github.ref }} is a fully qualified tag name in the form of
    refs/tags/<tag-name>. Since we're interested in the <tag-name>,
    we need to do a trick to extract the value from it.

1. Use `setup-node@v2` instead of `setup-node@v1`. We don't use any
   specific, but let's stick with newer version assuming it's there
   for a greater good.

2. Fix name of the uploaded release bundle. Apparently,
   `${{ github.ref }}` is a fully qualified tag name in the form of
   `refs/tags/<tag-name>`. Since we're interested in the `<tag-name>`,
   we need to do a trick to extract the value from it.
@ikalnytskyi ikalnytskyi requested a review from lotrien January 9, 2021 16:17
@lotrien lotrien merged commit f5a60e4 into master Jan 9, 2021
@lotrien lotrien deleted the gh-actions-improvements branch January 9, 2021 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants