Keeping up to date with new versions

[james]

The Platform API SDKs are regenerated against the Platform API after each deployment of the API to production. Because of this generation and deployment pipeline, the latest version of the SDK should always be used because it is the only version that exactly matches the contract of the API that’s live in production.

-- https://developer.mypurecloud.com/api/rest/versioning.html

How best should we keep up to date on new releases?

There have been 14 over the past 2.5 months, which is about 1 per week. Unlike many other CDNs, the GPC CDN URI does not appear to enable specification of only the major version, and automagically return the latest version matching that parameter. This means we need to change the major.minor.patch portion of the URI for every release. At the rate of release for the GPC Platform API, this requires quite a lot of attention by consuming developers.

Is there a strategy we may use that will not require us to be constantly monitoring and modifying the URI on a ~weekly basis?

[tim.smith]

While the best practice is always to use the latest version of the SDK, updating the SDK for every version isn't strictly necessary. If you keep an eye on the repo's releases, which also comes as an atom feed if you use a reader, you can check the release notes for each version to see if any APIs you're using are affected. If nothing your using was updated, you can safely ignore that version of the SDK.