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?

[GeoffreyFClark]

Make sure the workflow file is in the .github/workflows/ directory, verify the workflow syntax, check you're publishing a release (not just creating a tag). Does the "Actions" tab show any logs or errors? Also confirm that GitHub Actions is enabled, and check the workflow file's extension (e.g., .yml).

[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...

[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?

[sancheztornero]

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.

[sgsollie]

Suspect this is the real solution - we ran into this too and this worked for us.

[ad869]

Right answer, thanks

[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.

[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.

[mitbal]

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