Hi, On Mon, 2025-07-21 at 09:17 +0200, Konrad Windszus wrote: > Hi, > In the context of SLING-12861[1] the question arose how to promote an > unstable (0.x versioned) package version to a stable one without > breaking all consumers. > IIUC all bundle and package versions having major version 0 are > considered preliminary [2] by baselining and therefore will never > emit any errors even when modifying the API in a non backwards > compatible way without modifying the version. > I raised a ticket with Bnd[3] but while waiting for an answer there I > would like to know how the process used to be for other Sling modules > in the past. > Thanks in advance for any input.
I am not aware of history but I am in the same situation with the OAuth Client bundle which exports packages as 0.1 and marks them all as @ProviderType to generate narrow import ranges [4]. Now I wonder if exporting packages without a version would be better rather than setting 0.x versions. Thanks, Robert [4]: https://github.com/apache/sling-org-apache-sling-auth-oauth-client?tab=readme-ov-file#apache-sling-oauth-20-client-with-oidc-support
