Update and manage your published add-on

  • 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, seeUpdate, 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-ondeployment. From the Apps Script project, take the following steps:

    1. At the top, clickDeploy>Managedeployments.
    2. Select the active deployment to create a new version for and clickEdit.
    3. In theVersion section, selectNew version.
    4. ClickDeploy.
    Warning: Make sure that youdon't chooseNew deployment from theDeploy menu inStep 3.a. Creating a new deployment generates a newdeployment ID. If the add-on is updated to use thenew deployment ID, all existing triggers on the previously active deploymentare disabled.
  4. If you make changes that add scopes in your add-on's manifest, perform thefollowing steps:

    1. Update thescopeslisted in the Google Workspace Marketplace SDK and the OAuth consent screento match the scopes listed in the manifest.
    2. Submit a new request for OAuth verification from yourOAuth consent screen. If you don’treverify 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 theAppConfiguration page of the Google Workspace Marketplace SDK.

  6. ClickSave. Your new version is published.

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

To learn more about creating and managing versions seeVersions.

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-12-11 UTC.