Clarification on Updating `deployPercentage` Without Triggering Review

[Maxim Topciu]

Hello,

I'm seeking clarification on the Chrome Web Store Publish API documentation regarding the `deployPercentage` parameter when publishing an item.

In the **Optional query parameters** section for the `publish` method, the documentation states:

```

deployPercentage string

Provide deployPercentage for percentage of users who will receive an update to this version. Valid values are non-negative integers between 0 and 100. Regardless of the value provided, 100% of new user installs receive the latest version. Once provided, this value can only be increased for any given release. Note that using this API endpoint always triggers review, even if only the deploy percentage has been changed.

```

This suggests that using the API endpoint to update `deployPercentage` will always trigger a review, even if only the deploy percentage has changed.

However, in the **Request body** section under the `publish` method, the description for the `deployPercentage` property says:

```

deployPercentage string

Provide deployPercentage for percentage of users who will receive an update to this version. Valid values are non-negative integers between 0 and 100. Regardless of the value provided, 100% of new user installs receive the latest version. Once provided, this value can only be increased for any given release. Changes to just the deploy percentage won't trigger an additional review.

```

This indicates that changing only the `deployPercentage` won't trigger an additional review.

My question is: **How can I use the API to update the `deployPercentage` without triggering a review?**

It seems like Oliver tried to update the documentation according to a comment here:

https://groups.google.com/a/chromium.org/g/chromium-extensions/c/rrc59uGR_gg/m/x6r_beaiAgAJ

But the description is still not clear to me.

Could someone please clarify the correct way to update `deployPercentage` through the API without triggering a review? Is there a specific method or parameter I should use to achieve this?

Thank you!

[Patrick Kettner]

Hello Maxim,

It looks like it was just not updated in every section. As of now a review will always occur if you change it via API. Thank you for pointing it out, I will get the docs updated asap.

patrick

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/4f0329c6-68ac-4a7b-9830-bebe661d9c64n%40chromium.org.

[Maxim Topciu]

Thank you for the clarification, Patrick.

Could you please explain why it’s necessary for a review to be triggered when updating deployPercentage through the API, while doing so via the Developer Console does not initiate the review process?

Additionally, does the Chrome Web Store team have any plans to align the API behavior with the Developer Console, allowing deployPercentage updates without triggering a review? This feature would greatly streamline workflows for developers using the API.

Thank you!

[Patrick Kettner]

I do not have the historical context for why that would be the case, but I personally believe that it was just a bug. I do not know if the team has agreed to change that behavior, but I certainly am pushing for it to be changed.

[Maxim Topciu]

Ok, thank you! I hope they decide to change this.

[Maxim Topciu]

Patrick,
It came to my mind that it would be really helpful to have the option to specify deployPercentage during the update step, rather than only at publish time. In the Chrome Web Store console, we typically upload the new version, configure the deployment percentage, and then click publish.
If you have the opportunity, could you please pass along this idea to the Chrome Web Store team?
Thank you!

[Patrick Kettner]

Ill absolutely pass that along to the team, thank you for sharing!