We've added an additional confirmation before archiving plans and add-ons. Stigg app users are now required to enter the plan or add-on name to confirm the action.

We also added validations to prevent archiving of add-ons that are compatible with the latest published plan version. To archive them, first publish a plan version without the compatible add-on.

When a plan or add-on is archived, existing customers are un-affected; however, new subscriptions with those plans and add-ons can no longer be created.

We've made the "health" and "ready" endpoints of the Stigg Sidecar configurable to allow you to more easily integrate it to your existing monitoring infrastructure.

To do so, simply pass the HEALTH_ENDPOINT_URL and READY_ENDPOINT_URL environment variables when running the Sidecar instance.

More details about the available configuration options can be found here.

We've made it easier to get up and running with Stigg when using the Python SDK by providing visibility for all of the available SDK methods via an SDK reference.

The SDK reference is automatically updated whenever a new SDK version is published.

We've made it easier to get up and running with Stigg when using the Go SDK by providing visibility for all of the available SDK methods via an SDK reference.

The SDK reference is automatically updated whenever a new SDK version is published.

We've added a new API for listing customers' active subscriptions. The new API is accessible from Edge and has a significantly higher rate limit.

Listing customers' active subscriptions can now be achieved by the getActiveSubscriptionsList method. Getting the full data of each subscription can then be done using the getSubscription method.

The new API is available in the Stigg Node.js SDK v3.37.0, Stigg Python SDK v1.236.0, Stigg Go SDK v1.236.0, Stigg Java SDK v1.236.0, Stigg Ruby SDK v1.236.0, Stigg .NET SDK v.1236.0, Stigg Sidecar SDK v2.0.0, Stigg JavaScript SDK v3.20.0, Stigg React SDK v5.16.0, Stigg Vue.js SDK v4.5.0 and Stigg Embed SDK v5.6.0 or later.

We've improved the user experience for adding and updating plan and add-on entitlements! 🤩

Adding entitlements now takes place via side panel and includes a clearer path for adding multiple entitlements at the same time.

Once confirmed, the update takes place in the background and no longer causes a refresh of the entire screen.

When customers are subscribed to plans with pay-as-you-go pricing, usage of pay-as-you-go charges is synced from Stigg to Stripe every hour.

To allow easy debugging of the integration with Stigg, we've added the ability to manually sync usage from Stigg to Stripe directly from the Stigg app. To do so, open the relevant subscription in the Stigg app and click on the the "Sync usage to Stripe" action.

We've made the ability to copy the configuration of an environment to new and existing environments more accessible by allowing users to do so directly from the environment picker.

Copying environment configurations allows users to easily push pricing and packaging changes between environments - we call it "Git for pricing changes". 

Click here to learn more about this capability.

We've extended the Stigg SDK for Python to support both Pydantic v1 and Pydantic v2.

With this change, customers can use the latest version of the Pydantic framework together with the Stigg SDK. Customers that currently use Pydnatic v1 can plan the migration to Pydnatic v2 knowing that Stigg supports both framework versions.

This enhancement is supported in the Stigg SDK for Python v1.97.1 and Stigg Sidecar SDK v1.98.3 or later.

We've added an ability to view the prorated amount due today when creating new subscriptions in the Stigg app. 

The experience is similar to the one that was previously available when updating a subscription a subscription to a specific plan -changing billing period, unit quantity and add-ons.

Using the new interface, Stigg app users can determine the prorated amount due today also when creating subscription to a new plan.