Patch version as pre-release

[AxelMolina1]

Please, don't use patch versions for pre-release, most of repos are using "^" to auto update to latest patch version which switch to your pre-release versions.

We've been having issues with your pre-release versions (impossible to deploy on macOS since >26.0.12, signing step last forever) and it can be hard to track the breaking changes when it's just a patch version introducing bugs.

Thanks for listening to my demand.

[mmaietta]

impossible to deploy on macOS since >26.0.12, signing step last forever

Can you elaborate on this further? This seems worthwhile to investigate.

most of repos are using "^" to auto update to latest patch version which switch to your pre-release versions

Then don't? Pinning dependencies explicitly is, by default, the best approach from both a security and stability perspective.

More importantly, my main concern is regarding oversight of this project. What breaking changes have been introduced in a patch version?