2 Commits
Author SHA1 Message Date
lars dfff36b1d2 Use PACKAGE_DEPLOY_KEY PAT for plotstyle publish workflow
Publish plotstyle / build-and-publish (push) Successful in 7s
CI / test:pytest (push) Successful in 22s
CI / lint:ruff (push) Successful in 16s
CI / format:ruff (push) Successful in 15s
CI / typecheck:ty (push) Successful in 21s
CI / vulnerabilities:pip-audit (push) Successful in 18s
The built-in Actions token was rejected by the Gitea package registry
(401 reqPackageAccess); a PAT with write:package scope is required.
2026-07-24 11:04:31 +02:00
larsandClaude Sonnet 5 5109b6505c Move build system from setuptools to uv, wire uv into CI/CD
CI / lint:ruff (push) Successful in 25s
CI / format:ruff (push) Successful in 14s
CI / typecheck:ty (push) Successful in 15s
CI / vulnerabilities:pip-audit (push) Successful in 17s
CI / test:pytest (push) Successful in 24s
Convert both pyproject.toml files to the uv_build backend and turn the
repo into a proper uv workspace (plotstyle moved to src layout, since
uv_build requires the module in its own subdirectory). Dev tooling
moves from an optional-dependencies extra to a dependency-group, and
plotstyle's matplotlib dependency is now its own rather than a
gallery "plotting" extra.

Gitea Actions workflows and the Dockerfile now use astral-sh/setup-uv,
uv sync, uv run, uv build, and uv publish throughout instead of pip,
build, and twine. Also fixes .dockerignore, which was excluding
uv.lock, deploy/, and README.md and would have broken even the
previous Dockerfile's COPY of deploy/entrypoint.sh.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-24 10:30:20 +02:00