Tag name using environment variables

Question

I want to create a release tag from a workflow with GitHub Actions using actions/create-release@v1. I am specifying the same value for the tag name and the release name, which is v${MAJOR}.${MINOR}.${PATCH}, where MAJOR, MINOR, and PATCH are defined under env at the beginning of the yaml file before all jobs like this:

env:
  MAJOR: $(cat VERSION.txt | cut -d . -f 1)
  MINOR: $(cat VERSION.txt | cut -d . -f 2)
  PATCH: $(cat VERSION.txt | cut -d . -f 3)

Here is the part where I invoke the create-release action:

- name: Create Release
  uses: actions/create-release@v1
  env:
    GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} # this token is created by Actions, no need to set it up ourselves
  with:
    tag_name: "v${MAJOR}.${MINOR}.${PATCH}" #THIS DOESN'T CAST MAJOR, MINOR, PATCH
    release_name: "v${MAJOR}.${MINOR}.${PATCH}"

This creates a tag name that is explicitly v${MAJOR}.${MINOR}.${PATCH}. The environment variables are not converted to their values. When I use v${{ env.MAJOR }}.${{ env.MINOR }}.${{ env.PATCH }} instead, I get a not well-formed tag name.

When I echo v${MAJOR}.${MINOR}.${PATCH}, I get the desired output, which is something like v5.9.1.

How can I make the tag name use the values of the environment variables ?

Without the section where you are setting these variables it's just guessing — riQQ
– riQQ, Commented May 7, 2021 at 19:32
You can't set the env vars like that. Check out the docs here: docs.github.com/en/actions/reference/… — riQQ
– riQQ, Commented May 7, 2021 at 20:17
If I'm not mistaking, the syntax you are pointing works at a job level, meaning that I have to repeat it for each job, while setting the env key at the beginning of the yaml file before any job makes the environment variables available to all jobs. Also, the way I did seems to work for other actions in the same yaml file. — dada
– dada, Commented May 7, 2021 at 20:40

dada · Accepted Answer · 2021-05-08 07:33:54Z

0

Thanks to one of the comments, I managed to make tag_name receive the value v5.9.1. I removed the env key at the beginning of the yaml file, and created a step get_version with the following:

   - name: Get version
      id: get_version
      run:  |
        MAJOR=$(cat VERSION.txt | cut -d . -f 1)
        MINOR=$(cat VERSION.txt | cut -d . -f 2)
        PATCH=$(cat VERSION.txt | cut -d . -f 3)
        VERSION="v${MAJOR}.${MINOR}.${PATCH}"
        echo "::set-output name=version::${VERSION}"

then I modified the create release step :

- name: Create release
  uses: actions/create-release@v1
  env:
     GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
  tag_name: ${{ needs.get_version.outputs.version }} 
  release_name: ${{ needs.get_version.outputs.version }}
   draft: false
   prerelease: false

answered May 8, 2021 at 7:33

dada

1,5232 gold badges22 silver badges48 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Tag name using environment variables

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related