Skip to content

robostack-bot: update-pixi, a monthly pixi upgrade PR - #205

Merged
Tobias-Fischer merged 5 commits into
mainfrom
bot/update-pixi-command
Nov 9, 2026
Merged

Tobias-Fischer merged 5 commits into
mainfrom
bot/update-pixi-command

Conversation

@Tobias-Fischer

@Tobias-Fischer Tobias-Fischer commented Nov 9, 2026 •

Copy link
Copy Markdown
Collaborator

Like RoboStack/robostack.github.io's monthly Upgrade pixi dependencies PR (RoboStack/robostack.github.io#221), as a robostack-bot command so the PR is opened with the bot's token (CI runs on it) and gets the bot's usual summary/reply handling.

update-pixi (pixi run rs update-pixi, tools/maintenance.py):

  • pixi upgrade --json of the tooling's dependencies in pixi.toml / pixi.lock, run before pixi run (it reinstalls the environment; arguments from rs update-pixi --excludes, the JSON handed to rs update-pixi --changes, as in the closed robostack-bot: monthly upgrade-pixi PR for the tooling's dependencies #206); the PR body is pixi exec pixi-diff-to-markdown's table of the changes, then pixi run rs check.
  • Held back: python (a new minor comes before builds of everything the tooling needs; a trial bumped it to 3.15 with pyyaml falling back to PyPI on win-64) and every requirement that is only an upper bound (cmake = "<4.0", setuptools = "<82.0": deliberate caps). The vinca git pin stays update-vinca's.
  • Nothing newer: no PR.
  • The PR is labelled build:none (only the checks; remove the label to build), as robostack-bot: build:none on the update-vinca and update-build-timings PRs #207 does for the other bot PRs that change no package.

Triggers: monthly (29 5 1 * *, the plan job matches it like the weekly cron), workflow dispatch, issue form, @robostack-bot update-pixi (maintainers). README and the issue template list it.

Tested locally: pixi run test (3 new tests: parsing, what's held back, no PR without changes), rs check ok, and a real pixi run rs update-pixi run, which today would bump gh 2.103.3, pytest 9.2.0, rattler-index 0.34.5, git-lfs 3.8.1, m2-patch 2.8.1.1 (win-64), pyyaml/git builds, with rs check ✅ (those changes not committed here; the bot's first run will open that PR).

🤖 Generated with Claude Code

`pixi upgrade` of the tooling's dependencies (pixi.toml, pixi.lock), with
pixi-diff-to-markdown's table of the changes as the PR body, as in
robostack.github.io. Python and requirements that are only an upper bound
(cmake <4.0, setuptools <82.0) are held back; vinca stays update-vinca's.
Runs monthly (the 1st) and on demand.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Tobias-Fischer Tobias-Fischer added the build:none PR build: build no packages, only run the checks (tooling, CI or docs changes) label Nov 9, 2026
…s PRs

They touch files outside distros/, so CI would build every distribution, but
they change no package directly (the build times only change how jobs are
packed). Only the checks run now; a maintainer removes the label, or swaps it
for build:<distro> labels, to build. testpr reads the labels when its plan job
runs, so the label the bot adds right after opening the PR counts for the
first run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Tobias-Fischer and others added 2 commits November 9, 2026 16:52
pixi upgrade reinstalls the environment, so the bot runs it first (with the
--exclude arguments from `rs update-pixi --excludes`) and hands its JSON to
`rs update-pixi --changes`, which no longer upgrades under itself. Without
--changes, rs update-pixi still runs pixi upgrade (local use). From #206.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
# Conflicts:
#	README.md
#	tools/maintenance.py
@Tobias-Fischer
Tobias-Fischer merged commit 438b7d4 into main Nov 9, 2026
8 checks passed
@Tobias-Fischer
Tobias-Fischer deleted the bot/update-pixi-command branch November 9, 2026 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build:none PR build: build no packages, only run the checks (tooling, CI or docs changes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant