Pin the development version of ANTsPy for preview builds.

[muratmaga]

I need to keep the main for stable and pin the development to UI-updates branch for ANTsPy. The SlicerMorph change has already been incorporated.

[Copilot]

Pull request overview

This PR pins the development version of the ANTsPy extension for preview builds by updating the SCM revision from "main" to "UI-updates" branch.

• Changes the scm_revision field in the SlicerANTsPy extension catalog entry to point to the "UI-updates" development branch

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[lassoan]

It would be more clear to follow existing convention of making the extension's branch name match the corresponding Slicer core branch name. Is there a specific reason that prevents following this convention?

[muratmaga]

No not really. I want to make the development in UI-updates branch and do not want to touch main which is tied to the stable. But you are saying I should make a 5.10 branch from the current main and merge the UI-updated with main to follow the convention (so that I know what to do).

[lassoan]

Yes, we usually create a stable branch (e.g., 5.10) in the extension repository whenever the extension's main branch starts to get commits that are experimental or not compatible with the Slicer stable release.

[muratmaga]

I think it is correct now. There is a stable-5.10 branch for the stable and the UI-updates are merged with the main, and scm_revision is pointing to the main. Let me know if there anything I messed up.

[muratmaga]

So I guess, there is nothing to be merged in this case I suppose. Preview versions will use the main, and the stable will "automatically" use the stable-5.10 branches? If you can confirm it will great, as i want to use this model with few of the SlicerMorph extensions.

[muratmaga]

I am closing this. I have another PR #2267 that changes pins the stable versions to stable-5.10 branches.