Deprecating old Publish API

[vernak2539]

MSFT is deprecating the old v1 APIs used to publish chrome extensions. This was communicated via email to all developers with a deadline of 31/12/2024.

From the message below, this means the following are getting deprecated:

• secrets
• access token url

This will likely affect this package.

The blog post is here and the email sent is below.

Email

Hi,

You are receiving this email since you are currently consuming the Publish APIs in partner center to publish your Edge extensions.

As part of our commitment to improve our security methods and practices as part of the Microsoft Secure Future Initiative, we are making few changes to the Publish API for extension submission in Partner Center.

As part of this change, secrets are getting deprecated and replaced with API keys, Access Token URL is getting deprecated, and the API key expiration will reduce from 2 years to 72 days.

This feature is currently active on partner center and you can test it to ensure it works as desired. To enable new version of REST api, go to publish Api page and click on Enable button. The old v1 APIs will be getting deprecated on 31st Dec 2024.

Reference:
Blog with details of the change
Version 1 of APIs
Version 1.1 of APIs.
GitHub announcement

[sankalpmukim]

Hi, (I am not from the PlasmoHQ team)
As said in this issue, it does affect a large audience for an important utility.
Till now, I am one of the users of this package, using which my extension (https://github.com/sankalpmukim/aws-accounts-manager) proudly gets published to all 3 browser extension stores <3.
Because of that, I am trying my level best to get this package updated and migrated to the new v1.1 API.

As of now, I do not have any code exposure of this package or the above mentioned APIs, so I will be beginning studying the Old API, its usage in this package, and the new API. After an initial analysis of the amount of change required, it's wider impact (if any), and proposed solution, I will post my findings here and will hope to take this up to the finish line.

The reason I am posting this intro message here, is before I begin my analysis (know nothing as of now), if anyone else already has a headstart and can contribute with their ideas or experience, please join in!

@PlasmoHQ team's insights will be much appreciated!

[vernak2539]

@sankalpmukim I've had a go at starting here. As stated in the description, I'm unsure how to actually test this out (run the tests with the proper key file).

I'll likely also need to try to run this on a fake extension as well...