Submit a new request for OAuth verification from your OAuth consent screen. If you don’t
reverify your app before publishing the new version, a "This app isn't verified,"
warning is displayed to your users.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-28 UTC."],[[["\u003cp\u003eTo deploy a new version of your add-on, you need to make changes to the code, test it, and create a new version for deployment.\u003c/p\u003e\n"],["\u003cp\u003eWhen creating a new version, ensure you select "New version" instead of "New deployment" to avoid disabling existing triggers.\u003c/p\u003e\n"],["\u003cp\u003eIf you add new scopes to your add-on's manifest, you must update the scopes listed in the Google Workspace Marketplace SDK and the OAuth consent screen.\u003c/p\u003e\n"],["\u003cp\u003eFor Editor add-ons, update the version number on the App Configuration page of the Google Workspace Marketplace SDK.\u003c/p\u003e\n"],["\u003cp\u003eUsers do not need to reinstall the add-on for a new version, but they need to authorize any newly added scopes.\u003c/p\u003e\n"]]],["To deploy a new add-on version, modify the code and test it. Then, create a new version from the Apps Script project by managing deployments and selecting \"New version.\" Avoid creating a \"New deployment\" to prevent trigger disablement. If adding scopes, update them in the Google Workspace Marketplace SDK and submit a new OAuth verification request. Editor add-ons need a version number update. Finally, save the changes to publish the new version. Users will only need to authorize new scopes if added.\n"],null,[]]