Files

T

History

shcizo b1d6e5e705 fix: review fixes for webhook and auto mode (#8 )

Clear available_* only when the deployed ref equals it, drop the unused
poll source, stop leaking internal errors to CI, use the request-scoped
logger, validate X-Request-ID, re-read jobs once after the timeout,
report refused when no target ref exists, and tidy UI, deploy and docs.

2026-10-12 20:48:43 +02:00

action.yml

feat(action): reusable Gitea composite action for /update

2026-05-22 12:08:12 +02:00

README.md

fix: review fixes for webhook and auto mode (#8 )

2026-10-12 20:48:43 +02:00

README.md

Deploy via package-updater (composite action)

Notifies the package-updater master after a CI build. The master records the pushed version on every matching service and, for services in auto mode, updates them and waits for the result.

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 }}

endpoint is the master's /update, and UPDATER_TOKEN is the master's UPDATER_API_KEY. It 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. Auto services are updated to `<their image repo>:<tag>`, so it must exist in the registry. Omit it to re-pull the tag each service already follows.
`token`	yes	—	Bearer token configured in package-updater

Failure modes

The step exits non-zero on any HTTP 4xx or 5xx. This is intentional: the workflow surfaces the deploy failure to whoever pushed.

Code	Meaning
`200`	Every match was marked, updated, busy or refused. Manual services are only marked, which is not an error. A service that follows no tag is `refused` when the request has no `tag`.
`401`	Wrong or missing token.
`404`	No service uses the image. Check `image` for typos; matching is case-sensitive.
`500`	At least one auto job failed or timed out (`UPDATE_TIMEOUT` on the master).
`503`	The master has no `UPDATER_API_KEY`.

A request that matches both a working and a failed service now fails as a whole (500); the old single-instance updater's 207 no longer exists. The master waits for auto jobs, so the request can take minutes; raise any step timeout in your workflow accordingly.