docker-publish.yml

name: Docker publish

# Called directly from release.yml as a second job in the *same*
# workflow run (workflow_call), not triggered by the release event
# itself -- GitHub's anti-recursion rule means events performed with
# the default GITHUB_TOKEN (which release.yml uses to create the
# release) never trigger other workflows, confirmed empirically in
# sigennut before this repo got the same fix.
#
# workflow_dispatch lets this be re-run by hand for any already-tagged
# version, e.g. to backfill a release that predates this workflow:
#   gh workflow run docker-publish.yml -f version=0.1.0

on:
  workflow_call:
    inputs:
      version:
        required: true
        type: string
  workflow_dispatch:
    inputs:
      version:
        description: "Version to build and push (must match an existing git tag)"
        required: true
        type: string

permissions:
  contents: read
  packages: write

jobs:
  build-and-push:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
        with:
          ref: ${{ inputs.version }}

      - uses: docker/setup-qemu-action@v3
      - uses: docker/setup-buildx-action@v3

      - name: Log in to Docker Hub
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}

      - name: Log in to GHCR
        uses: docker/login-action@v3
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - name: Build and push
        uses: docker/build-push-action@v6
        with:
          context: .
          file: Dockerfile
          platforms: linux/amd64,linux/arm64
          push: true
          tags: |
            miklosbagi/invforge:${{ inputs.version }}
            miklosbagi/invforge:latest
            ghcr.io/miklosbagi/invforge:${{ inputs.version }}
            ghcr.io/miklosbagi/invforge:latest