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

..

bark-notify.sh

ci: move bark-notify.sh to .github/scripts, add Gitea release asset upload

2026-07-21 18:51:57 +08:00

create-release.sh

ci: extract release script to fix YAML parse error (line 51)

2026-07-21 18:57:18 +08:00