upload-release-asset | release asset via the GitHub Release API | Continous Integration library

I have this workflow: ci-cd.yml

My purpose is to:

1. Build and publish my code on any new tag
2. Create a release for that version
3. Upload the wheel into the release

So far step 1 and 2 are ok. Step 3 is giving me troubles.

Any help is welcome

I want to upload a artifact to latest release... without creating a new release.

I started with github official action upload-release-asset to upload artifact.
It requires a upload_url as an input which tells it the url of release.
Which is generally taken from creating a release in previous step with create-release action.

I tried to print output url from create_release-

I have a workflow where after a push to master I want to create a release and upload an asset to it.
I'm using actions/create-release@v1 and actions/upload-release-asset@v1.

I would like to pass the outputs of a bash commands to the action parameters. However I found out the syntax of "$(command)" does not work.

How can I pass the output of a bash command to an action's parameter.

For example I'd like to do something like this:

Background

I'm writing a Github action to upload build artefacts on every new tag created. This have turned out to be fairly strait forward to do.

However I wanted to upload the different variants as separate files to github's release page but couldn't figure out how to use a wildcard for this, and resorted to duplicating this sections with hardcoded filenames instead. To duplicate code with hardcoded filenames is error prone and not very future safe.

I guess the question maybe boils down to how yml works: Could this have been done shorter with some kind of a loop or wildcard?

This is the long code I ended up with:

I'm trying to write a workflow to have my GitHub project release populated by the tag creation workflow.

I already know how to create the release (using actions/create-release@v1.0.0) and how to push an artifact in the release (using actions/upload-release-asset).

But, since I'm building Rust code, I ahve to compile it on different platforms. Obviously, for that, I have one job per platform and I'm trying to push my artifact in that job.

But for the push to work, I have to use the release identifier given by actions/create-release@v1.0.0, which run in another job.

Hence my question : how can I pass the release URL from my release creation job to the job that will push artifact ?

THe full workflow is available here : https://github.com/Riduidel/rrss2imap/blob/master/.github/workflows/on_tag.yml

And I copy it here