Update and manage your published add-on

AI-generated Key Takeaways

• To 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.

• When creating a new version, ensure you select "New version" instead of "New deployment" to avoid disabling existing triggers.

• If 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.

• For Editor add-ons, update the version number on the App Configuration page of the Google Workspace Marketplace SDK.

• Users do not need to reinstall the add-on for a new version, but they need to authorize any newly added scopes.

Note: To change or unpublish your add-on’s Google Workspace Marketplace listing, see Update, unpublish, or check publication status.

To deploy a new version of your add-on’s code, follow the steps below.

1. Make the changes to your code.
2. Test the add-on using a head deployment.

3. When you’re ready to publish, create a new version for your add-on deployment. From the Apps Script project, take the following steps:

   1. At the top, click Deploy > Manage deployments.
   2. Select the active deployment to create a new version for and click Edit .
   3. In the Version section, select New version.
   4. Click Deploy.
   Warning: Make sure that you don't choose New deployment from the Deploy menu in Step 3.a. Creating a new deployment generates a new deployment ID. If the add-on is updated to use the new deployment ID, all existing triggers on the previously active deployment are disabled.

4. If you make changes that add scopes in your add-on's manifest, perform the following steps:

   1. Update the scopes listed in the Google Workspace Marketplace SDK and the OAuth consent screen to match the scopes listed in the manifest.
   2. 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.

5. If you’re updating an Editor add-on, update the version number on the App Configuration page of the Google Workspace Marketplace SDK.

6. Click Save. Your new version is published.

Your users don't need to reinstall the add-on, but if you added additional scopes, they need to authorize the new scopes.

To learn more about creating and managing versions see Versions.