2 Commits

Include renames

Author	SHA1	Message	Date
tao.chenandClaude	ac17a954b0	ci: extract release script to fix YAML parse error (line 51) ... The 'Upload release assets via Gitea API' step embedded a JSON heredoc inside a YAML block scalar (run: |). Gitea's YAML parser bailed at line 51 with 'could not find expected :'' when it saw the leading '{' of the JSON body — it tried to interpret the heredoc content as a flow mapping instead of literal text. Fix: move the release logic into .github/scripts/create-release.sh and pass the GitHub Actions context values as env vars. The step becomes: env: GITEA_TOKEN: ... TAG_NAME: ... API_URL: ... REPOSITORY: ... SHA: ... run: ./.github/scripts/create-release.sh Validates cleanly with PyYAML (yaml.safe_load). Pattern matches bark-notify.sh from earlier — CI helpers live in .github/scripts/, workflows stay slim. Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 18:57:18 +08:00
tao.chenandClaude	72fd363600	ci: move bark-notify.sh to .github/scripts, add Gitea release asset upload ... Two changes: 1. Move scripts/bark-notify.sh -> .github/scripts/bark-notify.sh (CI helper belongs next to the workflow that calls it). History preserved via git mv. 2. Add a 'Upload release assets via Gitea API' step that runs only on tag pushes (if: startsWith(github.ref, 'refs/tags/v')). It: - POSTs /releases to create a Gitea release bound to the tag - extracts the release id from the response (with explicit error path if the API call fails) - loops over dist/snapshot-*.whl and dist/snapshot-*.tar.gz and uploads each as a release asset Uses ${{ secrets.GITHUB_TOKEN }} exposed as the GITEA_TOKEN env var (the Gitea convention for the repo token secret). The Notify Bark step still runs last with if: always() so a release upload failure is reported via the phone. Co-Authored-By: Claude <noreply@anthropic.com>	2026-07-21 18:51:57 +08:00