From 97293fe50640c1fda5f708bef72cb77fe944edba Mon Sep 17 00:00:00 2001 From: Jeff Biseda Date: Thu, 18 May 2023 16:23:59 -0700 Subject: [PATCH] update frozen_abi dev workflow in docs (#31705) --- docs/src/implemented-proposals/abi-management.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/docs/src/implemented-proposals/abi-management.md b/docs/src/implemented-proposals/abi-management.md index f4b143db1..74505087d 100644 --- a/docs/src/implemented-proposals/abi-management.md +++ b/docs/src/implemented-proposals/abi-management.md @@ -73,6 +73,11 @@ To know the digest for new ABI items, developers can add `frozen_abi` with a random digest value and run the unit tests and replace it with the correct digest from the assertion test error message. +Run unit tests using the following command to generate digest values: +``` +SOLANA_ABI_DUMP_DIR=. cargo +nightly test abi +``` + In general, once we add `frozen_abi` and its change is published in the stable release channel, its digest should never change. If such a change is needed, we should opt for defining a new `struct` like `FooV1`. And special release flow