You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@answer.apache.org by li...@apache.org on 2024/01/23 08:00:48 UTC

(incubator-answer-website) 01/02: docs(plugin): additional notes on plugin upgrades #58

This is an automated email from the ASF dual-hosted git repository.

linkinstar pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-answer-website.git

commit 9a47b07fbc0b224b9bbd49ca40f6b4e0f58639d8
Author: LinkinStars <li...@foxmail.com>
AuthorDate: Tue Jan 23 15:08:11 2024 +0800

    docs(plugin): additional notes on plugin upgrades #58
---
 docs/guides/plugins.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/guides/plugins.md b/docs/guides/plugins.md
index 2216bc44..7811f8cc 100644
--- a/docs/guides/plugins.md
+++ b/docs/guides/plugins.md
@@ -103,7 +103,15 @@ The Answer with the plugin version is used in the same way as before. You can fi
 
 ## Upgrade
 
-You need build a new Answer binary with the new plugin version, then replace the old Answer binary with the new one.
+:::caution
+
+Note that if you are upgrading from a non-plugin version to a plugin version, you also need to execute the upgrade command (also considered as an upgrade).
+
+:::
+
+You need build a new Answer binary with the new plugin version, then replace the old Answer binary with the new one. As with normal upgrades, you need to execute different [upgrade steps](./upgrade) depending on the  deployment method. For example, if you are using binary deployment, you need to execute the `upgrade` command.
+
+
 
 ## Develop and contributing