A Smoother Development Experience: Introducing Our New API Versioning Strategy!

[angelo_mekenkamp]

I raised this concern when the new API versioning strategy was announced.

@angelo_mekenkamp

Also by labeling these versions according to years, I wonder if this will delay releases. Suppose you want to make a change to an API in July 2024. Will you now actually wait until it is January 2025 before releasing it?

I received the following response from SailPoint:

@colin_mckibben

Non breaking changes will be incorporated into production versions immediately. Users will not have to do anything on their end to get non-breaking changes. Breaking changes, however, will be put into a public preview in next year’s version, which can happen immediately. We do not have to wait for next year in order to release public preview APIs. Once we enter the next year (exact dates TBD), whatever is in public preview will become public.

but now, I saw the following annoucement:

@colin_mckibben

Given that 2025 is around the corner, the team has decided to hold off on implementing any new features until v2025.

So does this mean that SailPoint will not implement any new API features for the coming 3 months? Or will they still implement the new API features in these months, and still make them available to use, even in 2024, but only if we ensure that the endpoint is v2025 and apply the X-SailPoint-Experimental header?