Release publish is not triggering my github workflow

[Nuckerr]

Select Topic Area

Question

Body

So I have this github workflow setup:

name: Publish release

on:
  release:
    types: [published]

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      # Checkout the repository
      - name: Checkout code
        uses: actions/checkout@v2

      # Set up Java 17
      - name: Set up Java 17
        uses: actions/setup-java@v2
        with:
          java-version: 17
          distribution: 'adopt'

      # Make the Gradle wrapper executable
      - name: Make Gradle wrapper executable
        run: chmod +x gradlew

      # Run the gradle task
      - name: Run gradle task
        run: ./gradlew publishReleasePublicationToHangar -Pio.papermc.hangar-publish-plugin.default-api-key=${{ secrets.hangar-api-key }}

This is designed to run this gradle task when a release is created on github, however, after drafting a release with a tag and publishing it, the action does not run.
Its definitely configured correctly because I have a very similar workflow that runs on every commit but releases to a nightly channel. This leads me to believe that I am either releasing wrong or missing a piece of configuration (permissions maybe). Any ideas?

[Nuckerr]

Same directory as two other workflows that work fine that are triggered by commits.

And this is how I'm publishing the release

You can also see that there are no errors or warnings under the action.

And the fact that the other actions work means that its enabled right?

[epomatti]

Did you manage to fix this? Same issue here

[Nuckerr]

I ended up copying a friend's config, and I think the change that fixed it was making sure to use an array:

on:
  release:
    types: [published]

[epomatti]

hmmm.. well I have the same thing.. thanks for responding anyways. I'll see if the problem persists on my side.

[James-Mart]

But OP already has [published] as an array.... so that can't be what fixed it? Am I missing something?

[pgangloff-hbs]

This is NOT the fix. I have the same config, I want my action to trigger as soon as someone creates a new release on the github.com "create release" UI/console.And it is NOT triggering...

[pgangloff-hbs]

Just to update, I did get this (trigger a GitHub action when creating a new release on the github.com UI) to work some time ago with:

on:
  release:
    types:
      - published

[Nuckerr]

bump

[philmaas]

had the same issue.
I believe the issue was that the branch I wanted to create a release for was not the default-branch

Defining the branch seems to work, So the Jobs triggers when creating and publishing a release on that branch.

`name: Release 😎

on:
release:
types: [published]
branches: [main]`

[stilnox255]

this shoulb be marked as the correct answer.

[AllanOricil]

No, my main branch is the default one and it is not triggering the workflow when publishing a release.

https://github.com/AllanOricil/esp32-mfa-authenticator

[eugene-graft]

I have the same issue. Does anyone have a solution?

[ossanche]

Response #3

[yfukai]

I had a similar issue and finally noticed that I was trying to publish the repository with a tag at which the workflow *.yml file was still not committed. Hope this helps for those who found this thread with a similar trouble.

[BinaryVixen899]

Can also confirm that this was the right answer for me. Thank you very much!

[AllanOricil]

If you fix a CI after the tag, and you still use the tag it won't also trigger the job. I had to update the hash of my tag to one which had my ci fixes.

[kronnk]

This did it for me. Great answer! Thank you very much 👍

[sadrian]

Thanks a lot, I've spent many hours on this

[cmbuckley]

This was it for me! I had assumed the release event was one that checked for the workflow file on the default branch.

[narthanaj]

Still, I have the same issue ..!

[ngochieu642]

this thread has the answer for my case: https://github.com/orgs/community/discussions/25281

I was using the built-in secrets.GITHUB_TOKEN to publish a release
Because GitHub is designed in a way that it won't allow a workflow (represented by the token) to trigger another workflow, the release is not triggered

To solve this, create a PAT with enough permission to publish the release as yourself, this way other workflows based on Release event can be triggered

[jontze]

This is from my experience the correct answer for all of us that try to trigger the workflow based on a github release that is created by another github workflow.

[b4ird]

This was my experience, tested by manually creating a release which indeed did trigger the workflow as expected

[AlexanderArgyriou]

yep, you are right.

[lion3ls]

Yep, that was our issue too. This should be highlighted in the GitHub documentation.

[PrzemyslawSwiderski]

Right, at least some warning should be displayed...

[mitbal]

I encountered the same issue, and it turns out I use wrong directory name ('workflow' instead of 'workflows').

[LucBerge]

Is your release created by an other workflow?

If the answer is yes, then it is normal to see your workflow not beeing triggered.
See @stefreak's answer on #25281

[higaski]

Same issue for me, none of the suggestions worked.

[sesposito]

I've also observed this issue with a trigger on release "create". However I've also seen it fire a few times, and nothing has changed in the workflow config or release process creation between a successful trigger and none at all.

[Parsa3323]

Actually, I think it's because of the assets. In my experience, when I publish a release without assets, it works fine, but when I include assets during the initial publish, it doesn't. Try publishing the release first, then add the assets by editing it afterward

[paulmillr]

Same behavior here. event exists when no assets are published.

This is especially problematic with new GitHub Immutable Releases.

[Manuchandrasai]

• To allow automation-triggered releases to also trigger downstream release workflows, use a Personal Access Token (PAT) instead of the default GITHUB_TOKEN when creating releases in automated steps.

• Ensure your workflow has explicit permissions configured if it needs them:

permissions:
contents: write
pull-requests: write

• Check repository settings under Actions > General for "Workflow permissions" and "Allow GitHub Actions to create and approve pull requests".
• Review your release workflow's event types: types: [published] is correct for releases that are published (not just created or prereleased).

[jashwinsingh11]

The intention is for this workflow to run whenever I create and publish a GitHub release. I draft a release, attach the tag, publish it… but the workflow never triggers.

The workflow itself appears valid — I have a nearly identical one that runs on every commit and publishes to a nightly channel, and that one works fine. So I'm guessing I’m either:

• Publishing the release incorrectly, or
• Missing some type of configuration/permissions required for the release event.