Repository navigation
release: package set 0.4.0 (ScanImage connector out, host monitor quantized + cheaper sampling) - #7
Merged
Merged
Conversation
Both packages to 0.4.0 (one version for the set, CONTRACT §7.6): main carries, since 0.3.0, the ScanImage JSON connector's move to the private 2P rig repo (#4, a contract change: the /scanimage/* vocabulary left CONTRACT §2/§4), the host monitor's quantized typed HostStats floats and the cheaper portable process sampling (#6, proc_rescan_s / --proc-rescan), and the pixi 0.83 floor note in SETUP.md (#5). Bumped: package.xml, both package pixi.toml files, pyproject.toml, rig_nodes/__init__.py, the workspace pixi.toml, PACKAGE_SET_VERSION in the package-set workflow, the consumer recipe pins in README.md + SETUP.md, the CONTRACT version line (0.4.0, 2026-10-28), and the "release in progress" line in docs/host-monitor.md. pixi.lock unchanged (`pixi lock --check`). The channel payload + channel/README.md row follow in the release commit once CI is green. LAB-338 Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
The CI-built channel for 0.4.0 (144a0a8): rig_interfaces-0.4.0 for linux-64 / osx-arm64 / win-64, rig_nodes-0.4.0 noarch, repodata + shards, all pinned to ros2-distro-mutex 0.19 and Python 3.12; acceptance (clean-directory install + tests) passed on all three platforms. Added with `git add -f channel/*/` (the directories are gitignored). channel/README.md gets the 0.4.0 row and the sha256 table. The 0.3.0 payload files leave the tree in this commit: the post-release removal commit the README convention calls for was never made after 5e20dee, and the tagged URL raw.githubusercontent.com/…/v0.3.0/channel keeps serving them from history. Tag v0.4.0 goes on THIS commit. LAB-338. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Merged
6 of 7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Package set 0.4.0 for both
rig_interfacesandrig_nodes(one version, CONTRACT §7.6). LAB-338.What changed vs 0.3.0
reiserlab/scanimage-2026-bergamo2p-rig-nodes/):scanimage_node,scanimage_cmd,sims/si_json_mock, therig-scanimage-*/rig-si-mockconsole scripts and tasks, the ScanImage group oftest_device_nodes.py, the/scanimage/cmd|reply|statusvocabulary in CONTRACT §2/§4. A removed node is a contract change → minor bump. The generic/<src>/cmd|reply|statuscontract,ConnectorReplyand the outcome vocabulary stay.host_sampler.quantize+host_monitor.to_msground the typedHostStatsfloats to power-of-two steps (1/1024 for fractions and cores, 1/64 for everything else) so zstd can compress them (typed/rig/host6.7 % → 4.1 % of a ww18 harness bag); the portable (macOS/Linux) process sampler reads the whole process table everyproc_rescan_s(5 s,--proc-rescan) and only watched pids in between (lab Mac 6.7 % → well under 1 % of a core; ww18 forced-portable 24.9 % → 7.3 % mean)..msgchange:rig_interfaces0.4.0 carries the 0.3.0 messages, rebuilt under the new version.Release steps (README "Releasing a package set")
PACKAGE_SET_VERSION+ recipe pins + CONTRACT line (144a0a8)git add -f channel/*/+channel/README.mdrow and sha256 table (6aad10a; the 0.3.0 payload files leave the tree in the same commit — their post-release removal commit was never made, and thev0.3.0URL serves them from history)v0.4.0tagged on the payload commit 6aad10a and pushed;https://raw.githubusercontent.com/reiserlab/rig-nodes/v0.4.0/channel/win-64/rig_interfaces-0.4.0-ha41a7fa_0.conda→ HTTP 200 (194703 B), likewise osx-arm64 / linux-64 / noarch and the repodatarig/pixi.toml→ thev0.4.0tag URL,==0.4.0, re-locked with pixi 0.83; Mac verification in its body: harness 60 / 60, typed 63 / 63)Michael merges (sessions cannot). The payload may be removed from the tree in a later commit, as the recipe says; git history serves the tagged URL.
🤖 Generated with Claude Code