أرسِل طلبًا جديدًا لإثبات ملكية حساب OAuth من شاشة طلب الموافقة المتعلّقة ببروتوكول OAuth. إذا لم تتم
إعادة إثبات ملكية تطبيقك قبل نشر الإصدار الجديد، سيتم عرض تحذير "لم يتم إثبات ملكية هذا التطبيق"
للمستخدمين.
تاريخ التعديل الأخير: 2024-12-22 (حسب التوقيت العالمي المتفَّق عليه)
[null,null,["تاريخ التعديل الأخير: 2024-12-22 (حسب التوقيت العالمي المتفَّق عليه)"],[[["\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,["# Update and manage your published add-on\n\n| **Note:** To change or unpublish your add-on's Google Workspace Marketplace listing, see [Update, unpublish, or check publication status](/workspace/marketplace/manage-app-listing).\n\nTo deploy a new version of your add-on's code, follow the steps below.\n\n1. Make the changes to your code.\n2. Test the add-on using a head deployment.\n3. When you're ready to publish, create a new version for your add-on\n deployment. From the Apps Script project, take the following steps:\n\n 1. At the top, click **Deploy** \\\u003e **Manage\n deployments**.\n 2. Select the active deployment to create a new version for and click Edit edit.\n 3. In the **Version** section, select **New version**.\n 4. Click **Deploy**.\n\n | **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.\n4. If you make changes that add scopes in your add-on's manifest, perform the\n following steps:\n\n 1. Update the [scopes\n listed in the Google Workspace Marketplace SDK](/workspace/marketplace/enable-configure-sdk#oauth_scopes) and the OAuth consent screen to match the scopes listed in the manifest.\n 2. Submit a new request for OAuth verification from your [OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent/edit). If you don't reverify your app before publishing the new version, a \"This app isn't verified,\" warning is displayed to your users.\n5. If you're updating an Editor add-on, update the version number on the [App\n Configuration page of the Google Workspace Marketplace SDK](https://console.cloud.google.com/apis/api/appsmarket-component.googleapis.com/googleapps_sdk).\n\n6. Click **Save**. Your new version is published.\n\nYour users don't need to reinstall the add-on, but if you\nadded additional scopes, they need to authorize the new scopes.\n\nTo learn more about creating and managing versions see [Versions](/apps-script/guides/versions)."]]
