How can I get the generated version in a different step of the job?

[tfg2021-escinf-una]

Hey @PaulHatch, I'm using your action to generate the versions, however, I am not to sure in which variable does your action save the generated version.

If I use ${version} it is coming as blank. Could you please give me a hand?

The file I'm using contains the following commands:

[tfg2021-escinf-una]

Nevermind, I already figured it out.
Thanks!

[PaulHatch]

Great, for future reference, this was the use of single ${} instead of double ${{}}, right?

[PaulHatch]

Looks like you are trying to use the ${{ version }} directly in the action. You’d need to include the full path of the output you are trying to reference like ${{ steps.version.outputs.version }}.

…

On Jun 19, 2022, at 23:56, Amit Sengupta ***@***.***> wrote:  Hey Paul, Same question as the author above. I don't get the version in the last step. What am I missing? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.

[DechertNicholas]

For anyone still confused by this, I got it figured out. Add an id named version or whatever you want to your version step:

- name: Setup Versioning
      uses: paulhatch/[email protected]
      id: version
      with:
        # The prefix to use to identify tags
        tag_prefix: "v"
        # A string which, if present in a git commit, indicates that a change represents a
        # major (breaking) change, supports regular expressions wrapped with '/'
        major_pattern: "(MAJOR)"
        # Same as above except indicating a minor change, supports regular expressions wrapped with '/'
        minor_pattern: "(MINOR)"
        # A string to determine the format of the version output
        version_format: "${major}.${minor}.${patch}.${increment}"
        # If this is set to true, *every* commit will be treated as a new version.
        bump_each_commit: false
        # If true, the body of commits will also be searched for major/minor patterns to determine the version type.
        search_commit_body: true

Then access it as an environment variable, after specifically setting it as an environment variable in the env: section

- name: Set Package Version
      run: |
        ...
        Write-Output "Version: $env:FullVersion"
        ...
      env:
        FullVersion: ${{ steps.version.outputs.version }}

I'm sure there's also an easier way to do this, but for someone new to GithubActions, this wasn't immediately obvious to me.

[mortenn]

I don't see any mention of how to do this in the docs? I am new to github actions, so this "outputs" thing is completely unknown to me.

[DaneDH]

As @mortenn mentions, this is critical, this information needs to be in the documentation. How does one collect the outputs? Been searching the whole day. It seems like a secret.

[PaulHatch]

Outputs are a feature of GitHub Actions and are documented in the GitHub Actions documentation. Nevertheless, I've been kicking around the idea of adding full examples for specific platforms for some time, these could include examples of using different output from this job in real world scenarios.

[mortenn]

My pipeline was the first time I'd really used github actions, so I was completely clueless to outputs and didn't even know where to go to figure out what to do, but I did manage to figure it out eventually. for reference, here is my pipeline that uses the version in subsequent steps

[PaulHatch]

OK, so tbh I have been a bit more reserved about this as already the vast majority of tickets this project has received are about debugging people's pipelines rather than issues with the action itself and these requests are often quite tricky to debug because normally you can't see the build/repo, but I can give it a shot. I am planning to take some time in the next couple of weeks to work on version 6 and if I have time I'll add a couple of full examples.