Subscribe to the Chromium Extensions Google Group.

Also, identify breaking changes and regressions before they reach your users by developing and testing extensions in both the Chrome Stable and Canary channels. Monitor general extensions platform updates. Learn moreĬreate a rule that gives higher priority to emails with subjects with 'Announcement:' from addresses. Review the Chrome Enterprise release notes.Keep your extension code paths up to date and ensure you adhere to the current security and privacy requirements. Set up strong 2-Factor Authentication with a security key on accounts.Don’t let attackers hijack your extension and push malware to your users: This way, you won’t miss updates or warnings about take-downs if your extension is flagged for a violation.įor instructions, read Set up group publishing. Have a person in your organization read it. Do not filter email sent to the group.To avoid difficulties if an email address owner leaves your organization, do not use personal email addresses to publish extensions. If you can’t use group publishing, use your organization's email accounts to publish extensions.Keep the group private to only those who should publish the extension.Use the group publisher in the Chrome Web Store to manage the set of extension owners. The recommendations apply to extensions you publish for any user on the web (publicly) and users in your own organization only (privately). If you’re creating extensions and publishing them through the Chrome Web Store, follow these Chrome extension development guidelines. This article is for developers creating Chrome extensions for users in a business or a school.

Google chrome extension developer