tao.chenandClaude
121b835494
Replaces the previous five JupyterLab-template workflows (build / check-release / enforce-label / prep-release / publish-release / update-integration-tests) with a single minimal CI workflow tuned for a self-hosted Gitea runner. What's in the new build.yml: - Triggers: push to main, push of v* tag, pull_request - runs-on: astral-uv (self-hosted runner with uv pre-installed; we skip the setup-uv step) - Steps: checkout -> uv build -> upload-artifact - uv build alone is enough because pyproject.toml's [tool.hatch.build.hooks.jupyter-builder] drives jlpm install and jlpm build:prod before wheel assembly, and uv caches the build environment between runs. What's removed: all jupyter-server/jupyter_releaser steps and the check-links / update-snapshots / test_isolated / integration-tests jobs from the template — they depended on jupyterlab/maintainer-tools and GitHub-specific secrets (GITHUB_TOKEN, APP_PRIVATE_KEY, NPM_TOKEN) that don't apply to a Gitea deployment. Co-Authored-By: Claude <noreply@anthropic.com>
33 lines
716 B
YAML
33 lines
716 B
YAML
name: CI
|
|
|
|
on:
|
|
push:
|
|
branches:
|
|
- main
|
|
tags:
|
|
- 'v*'
|
|
pull_request:
|
|
|
|
jobs:
|
|
ci:
|
|
name: CI
|
|
# `astral-uv` is a self-hosted runner with uv pre-installed, so we can
|
|
# skip the setup-uv step entirely. pyproject.toml's
|
|
# [tool.hatch.build.hooks.jupyter-builder] handles jlpm install +
|
|
# jlpm build:prod before wheel assembly.
|
|
runs-on: astral-uv
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
|
|
- name: Build package
|
|
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
|