Adds two Gitea Actions scheduled workflows, each opening/updating one standing pull request (never pushing to master, never opening a Gitea issue) so the existing pull_request CI (lint/format/type-check/tests) gates every change before a human merges:
deps-lock.yml (weekly, Mondays): uv lock --upgrade within the existing pyproject.toml constraints, PR'd on chore/uv-lock-upgrade.
deps-bounds.yml (monthly): raises pyproject.toml upper bounds that have fallen behind the latest PyPI release, re-locks, PR'd on chore/dep-bounds. torch (pinned <2.4 for portal-machine driver support), plotstyle (private index), and the giant[...] self-references are permanently excluded from auto-raising.
Both branches are force-pushed fresh from master each run (no history accumulation, at most one open PR per job), sharing PR-upsert mechanics in deps-pr.sh. Both support workflow_dispatch for manual testing. No changes to ci.yml, release-commit.sh, .bumpversion.toml, or cliff.toml — merging either PR flows through the existing release job unchanged.
Prerequisite: secrets.CI_TOKEN's existing write:repository scope covers everything here — no new scope needed.
Adds two Gitea Actions scheduled workflows, each opening/updating one standing pull request (never pushing to master, never opening a Gitea issue) so the existing `pull_request` CI (lint/format/type-check/tests) gates every change before a human merges:
- **`deps-lock.yml`** (weekly, Mondays): `uv lock --upgrade` within the existing `pyproject.toml` constraints, PR'd on `chore/uv-lock-upgrade`.
- **`deps-bounds.yml`** (monthly): raises `pyproject.toml` upper bounds that have fallen behind the latest PyPI release, re-locks, PR'd on `chore/dep-bounds`. `torch` (pinned `<2.4` for portal-machine driver support), `plotstyle` (private index), and the `giant[...]` self-references are permanently excluded from auto-raising.
Both branches are force-pushed fresh from master each run (no history accumulation, at most one open PR per job), sharing PR-upsert mechanics in `deps-pr.sh`. Both support `workflow_dispatch` for manual testing. No changes to `ci.yml`, `release-commit.sh`, `.bumpversion.toml`, or `cliff.toml` — merging either PR flows through the existing release job unchanged.
Prerequisite: `secrets.CI_TOKEN`'s existing `write:repository` scope covers everything here — no new scope needed.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
https://claude.ai/code/session_01KhEer5EWzFU6NJi8hTnDe1
Adds two Gitea Actions scheduled workflows, each opening/updating one
standing pull request rather than pushing to master or opening an
issue, so the existing pull_request CI (lint/format/type-check/tests)
gates every change before a human merges:
- deps-lock.yml (weekly, Mondays): `uv lock --upgrade` within the
existing pyproject.toml constraints, PR'd on chore/uv-lock-upgrade.
- deps-bounds.yml (monthly): raises pyproject.toml upper bounds that
have fallen behind the latest PyPI release, re-locks, PR'd on
chore/dep-bounds. torch (pinned <2.4 for portal-machine driver
support), plotstyle (private index), and the giant[...]
self-references are permanently excluded.
Both branches are force-pushed fresh from master each run (no history
accumulation, at most one open PR per job), sharing PR-upsert
mechanics in deps-pr.sh. Both support workflow_dispatch for manual
testing. No changes to ci.yml, release-commit.sh, .bumpversion.toml,
or cliff.toml — merging either PR flows through the existing release
job unchanged.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KhEer5EWzFU6NJi8hTnDe1
lars
merged commit d1fb54fd09 into master2026-09-07 17:05:40 +02:00
lars
deleted branch feature/scheduled-dependency-bump2026-09-07 17:05:40 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Adds two Gitea Actions scheduled workflows, each opening/updating one standing pull request (never pushing to master, never opening a Gitea issue) so the existing
pull_requestCI (lint/format/type-check/tests) gates every change before a human merges:deps-lock.yml(weekly, Mondays):uv lock --upgradewithin the existingpyproject.tomlconstraints, PR'd onchore/uv-lock-upgrade.deps-bounds.yml(monthly): raisespyproject.tomlupper bounds that have fallen behind the latest PyPI release, re-locks, PR'd onchore/dep-bounds.torch(pinned<2.4for portal-machine driver support),plotstyle(private index), and thegiant[...]self-references are permanently excluded from auto-raising.Both branches are force-pushed fresh from master each run (no history accumulation, at most one open PR per job), sharing PR-upsert mechanics in
deps-pr.sh. Both supportworkflow_dispatchfor manual testing. No changes toci.yml,release-commit.sh,.bumpversion.toml, orcliff.toml— merging either PR flows through the existing release job unchanged.Prerequisite:
secrets.CI_TOKEN's existingwrite:repositoryscope covers everything here — no new scope needed.🤖 Generated with Claude Code
https://claude.ai/code/session_01KhEer5EWzFU6NJi8hTnDe1