Files
mizan/.gitea/workflows/publish-react.yaml
Ryth Azhur 9d2781b52c Catch missed content edits from tree restructure
The fe39fcb commit captured the file moves (git mv stages those automatically)
but didn't catch the content edits I made afterward — npm package rename
(@mizan/runtime → @mizan/base), path updates in Makefile/Dockerfile/examples,
and doc updates were all left unstaged at commit time.

This commit lands those:
- npm rename: 3 frontend package.jsons (base/vue/svelte) + mizan-base/src/index.ts + 4 codegen templates
- path updates: Makefile, Dockerfile.test, two Gitea workflows, four example/harness configs
- doc updates: CLAUDE.md, ROADMAP.md, ISSUES.md, docs/AFI_ARCHITECTURE.md

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-06 01:26:04 -04:00

37 lines
841 B
YAML

name: Publish React package to npm
on:
push:
tags:
- 'react/v*'
jobs:
publish:
runs-on: ubuntu-latest
defaults:
run:
working-directory: frontends/mizan-react
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '22'
- name: Install dependencies
run: npm ci
- name: Build
run: npm run build
- name: Configure Gitea npm registry
env:
REGISTRY_URL: ${{ gitea.server_url }}/api/packages/${{ gitea.repository_owner }}/npm/
PUBLISH_TOKEN: ${{ secrets.PUBLISH_TOKEN }}
run: |
npm config set @rythazhur:registry "${REGISTRY_URL}"
npm config set -- "${REGISTRY_URL#https:}:_authToken" "${PUBLISH_TOKEN}"
- name: Publish
run: npm publish