Build and release now run in one workflow on push to main: after the
build passes, if no tag exists for the package.json version, the image
is pushed and the tag and Gitea release are created. Running them in
sequence avoids the action-cache race between the separate build and
tag-triggered release workflows.
- Rename old release workflow to old_gitea-release.yaml
- Create new release.yaml with tag-based multi-arch Docker builds
- Update build.yaml with caching and PR triggers
- Use secrets.TOKEN for authentication
Generated by Mistral Vibe.
Co-Authored-By: Mistral Vibe <vibe@mistral.ai>
Sansan