add note for workflow ID changes on update

Author: khadni

src/content/cre/llms-full-go.txt

@@ -5644,6 +5644,11 @@ Last Updated: 2026-01-23
 
 When you update a deployed workflow, you redeploy it with the same workflow name. The new deployment replaces the previous version in the Workflow Registry contract. Currently, CRE does not maintain version history—each deployment overwrites the previous one.
 
+
+<Aside type="caution" title="Workflow ID changes on update">
+  The workflow ID changes each time you update a workflow. This is because the workflow ID is a hash derived from the workflow binary and configuration. If your consumer contract uses the workflow ID for validation, make sure to update the expected workflow ID after each update. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for details.
+</Aside>
+
 ## Prerequisites
 
 Before updating a deployed workflow, ensure you have:

src/content/cre/llms-full-ts.txt

@@ -4567,6 +4567,11 @@ Last Updated: 2026-01-23
 
 When you update a deployed workflow, you redeploy it with the same workflow name. The new deployment replaces the previous version in the Workflow Registry contract. Currently, CRE does not maintain version history—each deployment overwrites the previous one.
 
+
+<Aside type="caution" title="Workflow ID changes on update">
+  The workflow ID changes each time you update a workflow. This is because the workflow ID is a hash derived from the workflow binary and configuration. If your consumer contract uses the workflow ID for validation, make sure to update the expected workflow ID after each update. See [Building Consumer Contracts](/cre/guides/workflow/using-evm-client/onchain-write/building-consumer-contracts#34-configuring-permissions) for details.
+</Aside>
+
 ## Prerequisites
 
 Before updating a deployed workflow, ensure you have: