Skip to content

rig: pin rig-nodes 0.3.0 + re-lock with pixi 0.83 (#280, LAB-338) - #281

Merged
2 commits merged into
mainfrom
rig/pin-rig-nodes-0.3.0
Oct 29, 2026
Merged

2 commits merged into
mainfrom
rig/pin-rig-nodes-0.3.0

Conversation

@mbreiser

@mbreiser mbreiser commented Oct 28, 2026 •

Copy link
Copy Markdown
Contributor

Summary

rig/ installs the rig-nodes 0.3.0 package set (reiserlab/rig-nodes#3, CI run 40775301367 green on win-64 / osx-arm64 / linux-64 incl. the clean-directory acceptance): the rig_nodes / rig_interfaces pins → ==0.3.0, rig/pixi.lock re-locked with pixi 0.83 (the dev environment keeps its git source dependencies on rig-nodes main, never path dependencies).

Channel URL pinned by commit 5e20dee (the commit that carries the payload; the v0.3.0 tag was moved onto it on 2026-10-28, so the tag URL serves the same files and a later PR may switch the URL to the tag form). A commit SHA is as immutable as a tag.

What 0.3.0 brings to this workspace:

Closes #280 (LAB-338): the macOS floor moves from the deprecated [system-requirements] onto the platform entry (platforms = [{ name = "osx-arm64-macos-14-0", platform = "osx-arm64", macos = "14.0" }, "win-64", "linux-64"]; pixi requires a name distinct from the subdir for an entry that carries virtual packages, and this is the name pixi 0.80 itself wrote on ww18), requires-pixi = ">=0.80" makes an older pixi refuse instead of rewriting the lock, and the lock is written by pixi 0.83. The root pixi.toml / pixi.lock have no such skew (a plain pixi install on 0.83 leaves the root lock unchanged — checked).

Tier

next candidate (2026-10-28, with #269, #282 and the imaging-removal PR).

Release notes

none (nothing user-visible in the web tools; rig-side only).

Test plan (Mac, pixi 0.83, with ~/Documents/GitHub/rig-nodes renamed away so no sibling checkout can be picked up)

  • cd rig && pixi install --locked
  • pixi run test 59/59, pixi run -e typed test 62/62
  • pixi run -e typed check-typed lists DiskStats, GpuStats, HostStats, NetStats, ProcStats
  • git status rig/ clean after a plain pixi install
  • ww18: pixi install --locked leaves git status rig/ clean; pixi install -e typed imports rig_interfaces.msg.HostStats

LAB-338.

🤖 Generated with Claude Code

mbreiser and others added 2 commits October 28, 2026 17:28
…latform (#280, LAB-338)

Manifest only; the re-lock with pixi 0.83 follows once the v0.3.0 channel is tagged.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…`channel` feature (default/typed/viz), dev from git alone

Channel read at the payload commit 5e20dee (the v0.3.0 tag sits one commit early; moving it is a
one-liner for Michael). `dev` no longer includes `typed` and the rig_nodes pin is no longer a workspace
dependency: one package name from a git source and the channel does not solve once the released version
is ahead of rig-nodes main. Verified on the Mac with the sibling rig-nodes checkout renamed away:
`pixi install --locked` (default + typed), check-typed lists the eight message types, `pixi run test`
59/59, `pixi run -e typed test` 62/62. Closes #280. LAB-338.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
mbreiser added a commit that referenced this pull request Oct 28, 2026
mbreiser added a commit that referenced this pull request Oct 28, 2026
Candidate for Production. PRs: #281, #269, #282, #284.

Release-Manifest: releases/2026-10-28.json
@mbreiser mbreiser closed this pull request by merging all changes into main in 59a377b Oct 29, 2026
@mbreiser
mbreiser deleted the rig/pin-rig-nodes-0.3.0 branch October 29, 2026 00:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

rig/pixi.lock: re-lock with pixi >= 0.80 and pin requires-pixi (plain install on a rig rewrites the lock)

1 participant