Deploy via package-updater (composite action)

Notifies package-updater to docker compose pull + up -d for the matching service(s) after a CI build.

Usage

In a consumer repo's .gitea/workflows/deploy.yml:

jobs:
  deploy:
    runs-on: ubuntu-latest
    needs: [build-and-push]
    steps:
      - uses: gitea.example.com/shcizo/package-updater/gitea-action@v1
        with:
          endpoint: https://updater.example.com/update
          image: registry.example.com/${{ gitea.repository }}
          tag: ${{ gitea.sha }}
          token: ${{ secrets.UPDATER_TOKEN }}

UPDATER_TOKEN should be set as an organisation-level secret in Gitea so all repos share it.

Inputs

Name	Required	Default	Description
`endpoint`	yes	—	Full URL to `/update`
`image`	yes	—	Image reference without tag
`tag`	no	`""`	Tag that was just pushed (logged for audit)
`token`	yes	—	Bearer token configured in package-updater

Failure modes

The step exits non-zero if package-updater returns HTTP 4xx or 5xx. This is intentional — the workflow surfaces the deploy failure to whoever pushed.