DRAISegmentation: track main for Slicer 5.12 builds - #2407
Merged
lassoan merged 1 commit intoOct 1, 2026
Merged
Conversation
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
2 participants
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.
Update DRAISegmentation for Slicer 5.12 to track the source repository's
mainbranch instead of the fixed commit984c135. Daily Stable builds can then pick up tested source updates without a new index PR for each commit, as suggested in #2387 (comment). Both Stable and Preview intentionally track the same source branch.The source branch currently includes commit
c23890d, which updates the module's displayed name and descriptions to DRAI Segmentation and 3D Modeling. The extension identifier remainsDRAISegmentation.Validation: confirmed that the source branch exists; passed the index description validation (source checkout, schema, format, metadata, license, and dependencies) and confirmed that only
scm_revisionchanges. The source update passed Python syntax and Slicer 5.6.2 module-load checks, and its UI was reviewed locally. Cloud inference was not rerun for the branding-only update.