Enhancing the security of Microsoft Edge Extensions with the new Publish API – What’s next?

In our previous blog post, Enhancing the security of Microsoft Edge extensions with the new Publish API, we introduced the new Publish API, which brings key security enhancements to Microsoft Edge extension developers.

As mentioned in the Publish API documentation, support for the previous version of the API was planned to end on December 31, 2024. In this blog post, we’ll discuss the next steps and what extension developers need to do to ensure your extensions continue to function smoothly.

Extended deprecation period

Based on your feedback, we have extended the deprecation period. Support for the previous version of the Publish API will now end on January 10, 2025.

Starting on January 10, version 1 of the Publish API will be deprecated. Developers who have not yet transitioned to the new Publish API may experience disruptions in their continuous integration or delivery (CI/CD) pipelines, leading to updates not being published. This change is part of our ongoing commitment to enhancing the security of the publishing process and protecting your extensions.

What to do if you haven’t migrated to the new API yet

If you have not migrated your CI/CD code to use the new Publish API yet, your already published extensions will still function, but you won’t be able to publish new versions.

Start using the new Publish API as soon as possible as it is a significant step towards enhancing the security of your Microsoft Edge extensions.

To learn how to start using the new Publish API, please check out the updated documentation. In summary:

• Opt-in to the new API key management experience in Partner Center.
• Generate your Client ID and API key in Partner Center. The API key is valid for 72 days, compared to the previous 2-year expiration period. You will receive email notifications before your API key expires.
• In your CI/CD publishing code, instead of using the token that version 1 of the Publish API generated from credentials, use the Client ID and API key.
• Deprecate any old CI/CD pipelines that may be using the previous version of the API.

Share your feedback

We encourage you to share your feedback and questions on our GitHub developer community. Your input is invaluable in helping us improve the security and functionality of Microsoft Edge extensions.