[TaprootFreakAI]

EN:
Pull requests now land on develop, which publishes opencryptopay/api:beta, and main publishes :latest only through the release pull request.
CI uses the same gates as the 21.gifts API, with Bun pinned to 1.3.14.

DE:
Pull Requests landen auf develop, das opencryptopay/api:beta veröffentlicht, und main veröffentlicht :latest nur über den Release-Pull-Request.
Die CI hat dieselben Gates wie die 21.gifts-API, mit Bun 1.3.14.

Details

develop is the integration branch. A push there builds and pushes opencryptopay/api:beta and opens Release: develop -> main when develop is ahead. Merging that release push builds opencryptopay/api:latest.

The CI workflow is renamed to ci.yaml and names the same steps the 21.gifts API runs, without the Postgres job this service does not have. The pull request template lists those checks.

Image publish still needs the registry and dispatch secrets on this repository. They are not set, so the two deploy runs after the place-API merge stopped at registry login.

[TaprootFreakAI]

EN:
Three review rounds reached no remaining defects.
develop publishes the beta image and opens the release pull request, and main publishes the latest image.

DE:
Drei Review-Durchläufe, keine offenen Mängel.
develop veröffentlicht das Beta-Image und öffnet den Release-Pull-Request, main veröffentlicht das Latest-Image.

Details

Head 4c4090ffc87c3a9c01bccf9fe6b388b1ddd58479. CI is green on that commit: typecheck, lint, handbook, end-to-end check, coverage, build, and HTTP end-to-end.

The first rounds asked for bun run build in the readme and for CI on the develop push, because the release pull request is opened with the default token and that token does not start a new pull-request run. Both are in this head. The manual deploy button remains, and the contributing guide says it publishes the tag for the commit you start.