Pre-flight checks
action-gh-release version
v3.0.0
Runner operating system
ubuntu-latest
Release target repository
BenCurran98/ReleaseActionTest
Reproduction repo, gist, or artifact
https://github.com/BenCurran98/ReleaseActionTest
Workflow snippet
name: Pre Release
on:
workflow_dispatch:
jobs:
PreRelease:
permissions: write-all
runs-on: "ubuntu-latest"
steps:
- name: Get Tag
id: tag
uses: BenCurran98/actions-github-release@main
env:
token: ${{ secrets.GITHUB_TOKEN }}
repository: BenCurran98/ReleaseActionTest
type: "draft"
- name: Save Pre Release
uses: softprops/action-gh-release@v3
with:
token: "${{ secrets.GITHUB_TOKEN }}"
draft: ${{ null }}
prerelease: true
tag_name: "${{ steps.tag.outputs.release }}"
name: "${{ steps.tag.outputs.release }}"
Expected behavior
Prereleases should be able to be successfully created from previously made draft releases
Actual behavior
Workflow errors complaining about a release already existing for the supplied tag name
Steps to reproduce
- Trigger the draft release workflow with a specified tag name to create a draft release for a new tag
- Trigger the prerelease workflow which will grab the latest tag created in the draft release workflow and attempt to create a prerelease for it
Relevant logs
Draft release output: https://github.com/BenCurran98/ReleaseActionTest/actions/runs/25531805164/job/74939494324
Prerelease output: https://github.com/BenCurran98/ReleaseActionTest/actions/runs/25531822453/job/74939545897
Additional context
I believe this is a similar issue to what's reported in #772 and possibly #379
Pre-flight checks
masteraction-gh-release version
v3.0.0
Runner operating system
ubuntu-latest
Release target repository
BenCurran98/ReleaseActionTest
Reproduction repo, gist, or artifact
https://github.com/BenCurran98/ReleaseActionTest
Workflow snippet
Expected behavior
Prereleases should be able to be successfully created from previously made draft releases
Actual behavior
Workflow errors complaining about a release already existing for the supplied tag name
Steps to reproduce
Relevant logs
Additional context
I believe this is a similar issue to what's reported in #772 and possibly #379