Update and manage your published add-on

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

Make the changes to your code.
Test the add-on using a head deployment.
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.
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.
If you’re updating an Editor add-on, update the version number on the App Configuration page of the Google Workspace Marketplace SDK.
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.