tao.chenandClaude
f8c186fe2c
CI / CI (push) Failing after 11s
Replaces the self-hosted astral-uv runner (which had uv pre-installed) with the standard GitHub-hosted ubuntu-latest. Adds back the astral-sh/setup-uv step that was omitted in the self-hosted case. The astral-uv runner was timing out / unreachable from the GitHub Actions side; ubuntu-latest is universally available. Trade-off: ubuntu-latest runners start fresh each run (~30s cold start) and the setup-uv step takes a few seconds to download uv, versus a self-hosted runner that boots in <1s with uv ready. For a single CI job that runs on tag push only, the extra ~10s is not a problem. Co-Authored-By: Claude <noreply@anthropic.com>
73 lines
2.5 KiB
YAML
73 lines
2.5 KiB
YAML
name: CI
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
tags:
|
|
- 'v*'
|
|
pull_request:
|
|
|
|
jobs:
|
|
ci:
|
|
name: CI
|
|
# Standard GitHub-hosted ubuntu runner. uv is installed via the
|
|
# astral-sh/setup-uv action (one extra step vs. using a self-hosted
|
|
# runner with uv pre-installed, but matches what GitHub-hosted CI
|
|
# provides out of the box).
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Set up uv
|
|
uses: astral-sh/setup-uv@v6
|
|
with:
|
|
enable-cache: true
|
|
|
|
- name: Build package
|
|
env:
|
|
# Use the Tsinghua PyPI mirror for build-environment resolution;
|
|
# the runner is in China and the default pypi.org is too slow
|
|
# / unreliable for build dependency install.
|
|
UV_DEFAULT_INDEX: "https://pypi.tuna.tsinghua.edu.cn/simple/"
|
|
run: uv build
|
|
|
|
- name: Upload wheel artifacts
|
|
if: success()
|
|
uses: actions/upload-artifact@v4
|
|
with:
|
|
name: snapshot-dist
|
|
path: dist/snapshot-*
|
|
if-no-files-found: error
|
|
|
|
# Only create a release + attach dist/ assets when pushing a v* tag.
|
|
# On branch pushes / pull requests this step is skipped entirely.
|
|
# The release logic is in a separate script to avoid embedding a JSON
|
|
# heredoc inside a YAML block scalar (the previous version of this
|
|
# step was rejected by Gitea's YAML parser at line 51).
|
|
- name: Upload release assets via Gitea API
|
|
if: startsWith(github.ref, 'refs/tags/v')
|
|
env:
|
|
GITEA_TOKEN: ${{ secrets.GITHUB_TOKEN }}
|
|
TAG_NAME: ${{ github.ref_name }}
|
|
API_URL: ${{ github.api_url }}
|
|
REPOSITORY: ${{ github.repository }}
|
|
SHA: ${{ github.sha }}
|
|
run: ./.github/scripts/create-release.sh
|
|
|
|
# Always run, regardless of job status. The script is a side-effect;
|
|
# if the notification itself fails we swallow the error so CI does
|
|
# not turn red on a Bark outage.
|
|
- name: Notify Bark
|
|
if: always()
|
|
run: |
|
|
if [ "${{ job.status }}" = "success" ]; then
|
|
TITLE="✅ CI: ${{ github.repository }}@${{ github.ref_name }}"
|
|
BODY="Build OK for ${{ github.sha }} by ${{ github.actor }}"
|
|
else
|
|
TITLE="❌ CI: ${{ github.repository }}@${{ github.ref_name }}"
|
|
BODY="Build FAILED for ${{ github.sha }} by ${{ github.actor }}"
|
|
fi
|
|
./.github/scripts/bark-notify.sh "$TITLE" "$BODY" || echo "Bark notify failed (non-fatal)"
|