[upgrade] Proseg: bump v3.1.0 → v3.1.1 (patch release)
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 46
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
Current state
- Pinned: container
ghcr.io/dcjones/proseg:v3.1.0at modules/local/proseg/preset/main.nf:5 - Modules:
proseg/preset,proseg/proseg2baysor - Pipeline modes:
coordinate(default, when--methodis unspecified orproseg)
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).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the v3.1.1 release notes first, then update the pinned image in modules/local/proseg/preset/main.nf. Re-run the coordinate-mode tests with a Xenium v1 bundle on both tiled and non-tiled paths; done means the pin is v3.1.1 and both paths pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- bioinformatics, devops
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- Half a day
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 76/100