How to trigger a GitHub Actions workflow after the semantic-release has created a release.

[matzar]

I'm trying to set-up Docker Build and Push workflow when a new release is created with semantic-release.

This is my release.yml workflow:

name: Release
on:
  push:
    branches:
      - main
jobs:
  release:
    name: Release
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Setup npmrc
        run: |
          echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_TOKEN }}" > .npmrc
      - name: Install Dependencies
        run: npm ci
      - name: Build
        run: npm run build --omit=dev
      - name: Release
        run: npx semantic-release
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

And this is how it try to invoke docker-build-and-publish.yml workflow:

name: Build and Push Docker Image

on: 
  release:
    types: [published]
jobs:
# ...

I've tried bypassing it by targeting tag creation but no luck. Is semantic-release not triggering the release event, even though it's releasing a package? Funny thing is, that when I create a release manually, docker-build-and-publish.yml workflow triggers with the above on settings.

[albatarnik]

@matzar I have exactly the same issue, did you find a solution?

[gr2m]

The problem is

          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} 

Events triggered by GitHub Actions (using secrets.GITHUB_TOKEN) do not trigger further events

When you use the repository's GITHUB_TOKEN to perform tasks, events triggered by the GITHUB_TOKEN, with the exception of workflow_dispatch and repository_dispatch, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository's GITHUB_TOKEN, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.

https://docs.github.com/en/actions/security-guides/automatic-token-authentication#using-the-github_token-in-a-workflow

In order to trigger another workflow, you need to use a different means of authentication, like a personal access token or a dedicated GitHub App.