ci: automatic draft release creation on tag push

[gilcu3]

Closes #1971, supersedes #2203

This was tested in https://github.com/near/mpc-release-test
with release in https://github.com/near/mpc-release-test/releases/tag/untagged-c32331a90dc143d4acc8

[gilcu3]

this is needed as there was a collision when calling from another workflow

[claude]

Code Review

Reviewed the new release.yml workflow and the modifications to docker_launcher_release.yml and docker_node_release.yml.

The changes are clean: existing retag workflows are extended with workflow_call triggers, github.event.inputs correctly updated to inputs (works for both dispatch and call contexts), concurrency groups hardcoded to avoid collisions, and the new release orchestrator handles both tag-push and merged-release-PR triggers with proper semver validation.

No critical issues found.

✅

[SimonRastikian]

This looks good to me. I couldnt find however where the CI triggers when a tag is created (whether on main or in a branch)

[gilcu3]

This looks good to me. I couldnt find however where the CI triggers when a tag is created (whether on main or in a branch)

it applies when a tag is pushed anywhere

on:
  push:
    tags:
      - '*.*.*'

[netrome]

Nice stuff! Looking forward to seeing this in action!

[netrome]

Is this needed or is this just a nice to have simplification?

[gilcu3]

I think it might be, because of workflow_call, it is used like this in the examples at least.

[netrome]

Hmm, I wonder if it would make sense to generate the changelog here with git-cliff. But I think this is fine for now. I also want to keep our actions as simple as possible.