From a654504cd5c7a2f1cb5e7742c654fa356477c9b9 Mon Sep 17 00:00:00 2001
From: Stanley Chin <stan.chin@zapier.com>
Date: Tue, 9 Apr 2024 10:52:49 -0400
Subject: [PATCH 1/2] visual builder had this


From ff8032cd6ea28bfe6a9107a73a9f7e980e09d626 Mon Sep 17 00:00:00 2001
From: Stanley Chin <stan.chin@zapier.com>
Date: Tue, 9 Apr 2024 11:05:08 -0400
Subject: [PATCH 2/2] did it go through

---
 docs/cli.html                              | 2 +-
 docs/cli.md                                | 2 ++
 packages/cli/docs/cli.html                 | 2 +-
 packages/cli/docs/cli.md                   | 2 ++
 packages/cli/src/oclif/commands/promote.js | 2 ++
 5 files changed, 8 insertions(+), 2 deletions(-)

diff --git a/docs/cli.html b/docs/cli.html
index 5573e7415..5d0ade0c5 100644
--- a/docs/cli.html
+++ b/docs/cli.html
@@ -840,7 +840,7 @@ <h2 id="promote">promote</h2>
 </li>
 <li><p>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</p>
 </li>
-</ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
+</ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>After a promotion, go to your developer platform to <a href="https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues">close issues that were resolved</a> in the updated version.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>version</code> | The version you want to promote.</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-y, --yes</code> | Automatically answer &quot;yes&quot; to any prompts. Useful if you want to avoid interactive prompts to run this command in CI.</li>
diff --git a/docs/cli.md b/docs/cli.md
index 434fafd2f..f3273503c 100644
--- a/docs/cli.md
+++ b/docs/cli.md
@@ -403,6 +403,8 @@ Promote an integration version into production (non-private) rotation, which mea
 
 Promotes are an inherently safe operation for all existing users of your integration.
 
+After a promotion, go to your developer platform to [close issues that were resolved](https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues) in the updated version.
+
 If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.
 
 Check `zapier jobs` to track the status of the promotion. Or use `zapier history` if you want to see older jobs.
diff --git a/packages/cli/docs/cli.html b/packages/cli/docs/cli.html
index 5573e7415..5d0ade0c5 100644
--- a/packages/cli/docs/cli.html
+++ b/packages/cli/docs/cli.html
@@ -840,7 +840,7 @@ <h2 id="promote">promote</h2>
 </li>
 <li><p>This does <strong>NOT</strong> recommend old users stop using this version - <code>zapier deprecate 1.0.0 2017-01-01</code> does that.</p>
 </li>
-</ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
+</ul><p>Promotes are an inherently safe operation for all existing users of your integration.</p><p>After a promotion, go to your developer platform to <a href="https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues">close issues that were resolved</a> in the updated version.</p><p>If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.</p><p>Check <code>zapier jobs</code> to track the status of the promotion. Or use <code>zapier history</code> if you want to see older jobs.</p><p><strong>Arguments</strong></p><ul>
 <li>(required) <code>version</code> | The version you want to promote.</li>
 </ul><p><strong>Flags</strong></p><ul>
 <li><code>-y, --yes</code> | Automatically answer &quot;yes&quot; to any prompts. Useful if you want to avoid interactive prompts to run this command in CI.</li>
diff --git a/packages/cli/docs/cli.md b/packages/cli/docs/cli.md
index 434fafd2f..f3273503c 100644
--- a/packages/cli/docs/cli.md
+++ b/packages/cli/docs/cli.md
@@ -403,6 +403,8 @@ Promote an integration version into production (non-private) rotation, which mea
 
 Promotes are an inherently safe operation for all existing users of your integration.
 
+After a promotion, go to your developer platform to [close issues that were resolved](https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues) in the updated version.
+
 If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.
 
 Check `zapier jobs` to track the status of the promotion. Or use `zapier history` if you want to see older jobs.
diff --git a/packages/cli/src/oclif/commands/promote.js b/packages/cli/src/oclif/commands/promote.js
index bb3208db8..947b49f6e 100644
--- a/packages/cli/src/oclif/commands/promote.js
+++ b/packages/cli/src/oclif/commands/promote.js
@@ -248,6 +248,8 @@ Promote an integration version into production (non-private) rotation, which mea
 
 Promotes are an inherently safe operation for all existing users of your integration.
 
+After a promotion, go to your developer platform to [close issues that were resolved](https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues) in the updated version.
+
 If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.
 
 Check \`zapier jobs\` to track the status of the promotion. Or use \`zapier history\` if you want to see older jobs.`;