Forgejo Actions step that downloads the AnnoBase release named in the app settings
Find a file
Gergo 18bca6fab3 An AnnoBase folder left by the old archive fetch is moved aside like one of this step
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 13:19:17 +01:00
action.yml Build the listed AnnoBase frontend packages after the download; settings and destination relative to the workspace 2026-11-19 13:15:22 +01:00
fetch.py An AnnoBase folder left by the old archive fetch is moved aside like one of this step 2026-11-19 13:19:17 +01:00
README.md Build the listed AnnoBase frontend packages after the download; settings and destination relative to the workspace 2026-11-19 13:15:22 +01:00

annobase-fetch

Forgejo Actions step that puts the AnnoBase release named in the app settings next to the app.

- uses: https://git.annodev.software/annodev/annobase-fetch@v1
  with:
    settings: Product/backend/Product.Api/appsettings.json
    token: ${{ secrets.ANNOBASE_TOKEN }}
  • settings: JSON file of the app, relative to the workspace. It holds "AnnoBase": { "Version": "1.0.4" } (backend appsettings.json) or "annobase": { "version": "1.0.4" } with key: annobase.version (frontend package.json).
  • token: the organisation secret ANNOBASE_TOKEN (read-only token of the annobase-ci user for annodev/anno-base).
  • frontend-packages: AnnoBase frontend packages to build after the download (bun install --frozen-lockfile, then bun run --cwd packages/<name> build), for example api react map. Empty for backend jobs.
  • destination: default <workspace>/AnnoBase, which is where the AnnoBaseBackendPath and frontend link: paths of the products point.

The step reads release v<version> of annodev/anno-base, downloads manifest.json and the archive it names, checks the sha256 and unpacks the archive. AnnoBase itself stays private; this repository holds only the download step.