[Action required - PDP integrations] Replace Provenance SDK URL

We have introduced our CDN to improve the reliability of Provenance widgets on your website.

If you are showing Provenance Bundle on your website and load it as a script from unpkg.com you need to change the URL. Please follow the instructions below.

• Locate the script tag that loads Provenance SDK in your templates. You can search your code for unpkg.com/@provenance string. It may look like this:

<script defer src="https://unpkg.com/@provenance/provenance-sdk@1/dist/provenance-sdk.js"></script>

• Replace the URL in the src attribute to https://lib.provenance.org/sdk/@1/provenance-sdk.js . The entire script tag should look like:

<script defer src="https://lib.provenance.org/sdk/@1/provenance-sdk.js"></script>

We recommend this way of adding Provenance to your website because it is convenient and allows you to receive updates without needing to manage version number.

If you want more control over what version to use or what type of module, or your src attribute looks different to the example above then continue to the following section.

If your script tag looks different

1. Understand what type of module you are using. If the src attribute ends with contains provenance-sdk.js, then you are using CJS module. If the script tag has type="module" attribute and/or the src attribute ends with main.mjs, then you are using ESM
2. Understand what version you are using. If the src attribute contains provenance-sdk@1/dist then you are using the latest version. Otherwise, you are using a specified version.
3. Based on the type of module and version, select the URL from the table below. Note that 1.27.6 is the minimal version available through our new CDN:

If you haven’t found any script tags with Provenance SDK

This means that you are either not displaying Provenance content on your product pages or using it as an npm package. In this case, no action is needed.

FAQ

Why is this change needed?

Earlier, we suggested using unpkg.com as a simple way to add Provenance to your website. Unfortunately, Unpkg experienced issues that lasted for several days from 19 March 20:00 to 22 March 01:00 GMT. During the incident, Provenance Widgets weren’t displayed on the websites.

This made us rethink our approach to distributing the Provenance SDK. So, we introduced our own CDN that has better availability, allows us to continuously monitor its health and provides more control.

What will happen to the old way?

Our SDK is still available through unpkg.com, but it is less reliable.

What if I specified provenance as a dependency in package.json?

This approach is not affected by this change. If you want to use a specific version for compliance reasons or want to have more control, we recommend you keep using the SDK through npm or yarn.

How do I know what versions are available via the new CDN?

All versions starting from 1.27.6 will be available. You can check https://www.npmjs.com/package/@provenance/provenance-sdk?activeTab=versions