[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-22(UTC)"],[[["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."]]],["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"]]