## Current state - Pinned: container `ghcr.io/dcjones/proseg:v3.1.0` at [modules/local/proseg/preset/main.nf:5](https://github.com/nf-core/spatialaxe/blob/dev/modules/local/proseg/preset/main.nf#L5) - Modules: `proseg/preset`, `proseg/proseg2baysor` - Pipeline modes: `coordinate` (default, when `--method` is unspecified or `proseg`) ## Latest upstream - **v3.1.1** (released 2026-03-12): https://github.com/dcjones/proseg/releases/tag/v3.1.1 - v3.1.0 (released 2025-12-19) — current pin - 3-month gap between releases ## Why bump - Patch version → low risk - Stay current with upstream bug fixes - Container already published on `ghcr.io/dcjones/proseg` — no Wave/nf-core build needed ## Migration plan - [ ] Read v3.1.1 release notes (https://github.com/dcjones/proseg/releases/tag/v3.1.1) to confirm scope - [ ] Bump container to `ghcr.io/dcjones/proseg:v3.1.1` - [ ] Re-run coordinate-mode tests on a Xenium v1 bundle (both tiled and non-tiled paths) ## Risks - Patch release — low risk - No expected CLI changes ## Cross-links - Triggered by: Atera compatibility session 2026-05-28 (broader tool inventory check).
Current state
ghcr.io/dcjones/proseg:v3.1.0at modules/local/proseg/preset/main.nf:5proseg/preset,proseg/proseg2baysorcoordinate(default, when--methodis unspecified orproseg)Latest upstream
Why bump
ghcr.io/dcjones/proseg— no Wave/nf-core build neededMigration plan
ghcr.io/dcjones/proseg:v3.1.1Risks
Cross-links