Describe the improvement
When an Edge extension is successfully published, the confirmation email says that the product is “now available” and has been “successfully published”, but it does not identify which version was published.
This becomes confusing when multiple updates are processed close together. For example, I received several publication confirmations for StockBlocker today, but the emails themselves do not let me verify whether version 1.28.3 is the version that actually went live.
Expected behavior
Please include the published extension version directly in the publication confirmation email.
For example:
- Extension: StockBlocker
- Version: 1.28.3
- Status: Published
Comparison
Chrome Web Store already includes the item name, item ID, version, visibility, and published item link in its publication email.
Adding the version number to the Edge email would make release verification much clearer and avoid requiring developers to separately check Partner Center or the installed extension after every publication.
Describe the improvement
When an Edge extension is successfully published, the confirmation email says that the product is “now available” and has been “successfully published”, but it does not identify which version was published.
This becomes confusing when multiple updates are processed close together. For example, I received several publication confirmations for StockBlocker today, but the emails themselves do not let me verify whether version 1.28.3 is the version that actually went live.
Expected behavior
Please include the published extension version directly in the publication confirmation email.
For example:
Comparison
Chrome Web Store already includes the item name, item ID, version, visibility, and published item link in its publication email.
Adding the version number to the Edge email would make release verification much clearer and avoid requiring developers to separately check Partner Center or the installed extension after every publication.