Skip to content

New v2.5.0 feature prevents prereleased event trigger for a separate workflow #708

@krajewf

Description

@krajewf

According to the GitHub documentation for the release trigger:

"The prereleased type will not trigger for pre-releases published from draft releases, but the published type will trigger."

I have a workflow that runs with:

on:
  release:
    types: [prereleased]

This workflow no longer triggers when using v2.5.0 I assume because the original pre-release is first a draft before it is published. I only want my workflow to run on prereleased and not have to change my separate workflows to using the published type and an explicit check for the release type in all of the jobs if: github.event.release.prerelease == true

Is there a way to continue to have a prerelease published directly without being a draft first to continue to have the prereleased event trigger on a prerelease?

💭 Maybe a feature flag such as immutable: true will operate on the draft first then publish where immutable: false will operate like pre-v2.5 to maintain backward compatibility at least with regard to how the prereleased type is triggered.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions