stroblmeandClaude Opus 5
d4a9406c51
Docs / docs (push) Successful in 49s
Playwright Tests / test-playwright (1, 2) (push) Failing after 1m11s
Playwright Tests / test-playwright (2, 2) (push) Failing after 23s
pre-commit / pre-commit (push) Successful in 3m2s
Test Backend / test-backend (push) Successful in 2m22s
Compose Smoke Test / test-compose (push) Failing after 22s
Playwright Tests / merge-reports (push) Canceled after 1s
The gates have never gone green on the new runners. Three separate reasons: - backend/Dockerfile shipped Python 3.10 while the code imports typing.Self and datetime.UTC, so the container exited on import and the suite could not even load its conftest. The image moves to 3.13 and the packages declare >=3.12, which is the floor the tests actually pass on; ruff's target follows and rewrites timezone.utc and asyncio.TimeoutError accordingly. Relocking drops the 3.10 branch, which bumps FastAPI and so regenerates the SDK. - frontend/README.md had no trailing newline and two dashboard widgets used arbitrary text-[…] sizes. Both are em-relative on purpose, so they move to the inline style the neighbouring ramp already uses. - Every commit left its own run queued: without a concurrency group a runner that was offline for a while works through a backlog nobody reads. A stack that fails to come up now prints its logs before the teardown removes it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
57 lines
2.1 KiB
YAML
57 lines
2.1 KiB
YAML
# Publish both distributions to PyPI on a version tag.
|
|
#
|
|
# Tags are the trigger rather than pushes to main: a release is a decision, and
|
|
# a version already on PyPI cannot be replaced.
|
|
name: Publish
|
|
|
|
on:
|
|
push:
|
|
tags:
|
|
- "v*"
|
|
|
|
jobs:
|
|
publish:
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- name: Checkout
|
|
uses: actions/checkout@v4
|
|
- name: Set up Python
|
|
uses: actions/setup-python@v5
|
|
with:
|
|
python-version: "3.13"
|
|
- name: Set up uv
|
|
uses: astral-sh/setup-uv@v7
|
|
- name: The tag is what the packages say they are
|
|
# Publishing 0.2.0 from a v0.3.0 tag is the kind of thing nobody
|
|
# notices until an install pulls the wrong one.
|
|
run: |
|
|
version="${GITHUB_REF_NAME#v}"
|
|
for project in backend worker; do
|
|
declared=$(uv version --short --directory "$project")
|
|
[ "$declared" = "$version" ] || {
|
|
echo "$project declares $declared, tag says $version" >&2
|
|
exit 1
|
|
}
|
|
done
|
|
- run: uv build --all-packages --out-dir dist
|
|
- name: Both wheels install and run
|
|
run: |
|
|
uv run --no-project --with dist/fluksio_worker-*.whl fluksio-worker --help
|
|
uv run --no-project --with dist/fluksio-*.whl --with dist/fluksio_worker-*.whl \
|
|
fluksio --version
|
|
- name: Publish
|
|
env:
|
|
UV_PUBLISH_TOKEN: ${{ secrets.PYPI_TOKEN }}
|
|
# The worker first: `fluksio` depends on it, and for the seconds
|
|
# between two uploads the other order leaves a dependency that cannot
|
|
# be resolved — which on a first release is the whole of the window in
|
|
# which the package exists at all.
|
|
#
|
|
# `--check-url` makes a re-run skip what is already up there rather
|
|
# than failing on it, so a job that died between the two uploads can
|
|
# simply be run again. A version on PyPI can never be replaced, and
|
|
# this is the difference between retrying and burning a version.
|
|
run: |
|
|
uv publish --check-url https://pypi.org/simple/ dist/fluksio_worker-*
|
|
uv publish --check-url https://pypi.org/simple/ dist/fluksio-0*
|