Changelog

This patch release introduces a change to custom token deployment to distinguish them from native interchain tokens deployed by ITS.

Custom tokens using mint/burn will now have to use the updated MINT_BURN token manager type (i.e 4 enum value).
Custom tokens using MINT_BURN or MINT_BURN_FROM token manager types will need to give mint permission to the corresponding token manager contract instead of ITS. The token manager address corresponding to a tokenId can be predicted via the tokenManagerAddress query and tokenId can be computed via this query.
Native interchain tokens deployed by ITS will use the NATIVE_INTERCHAIN_TOKEN token manager type (i.e 0 enum value).
deployTokenManager will now revert if 0 token manager type is provided. All other token manager types will work as expected.
Existing custom tokens deployed with 0 token manager type will still work as expected. Although, when deploying the same token on a new chain, the new 4 (MINT_BURN) token manager type will need to be used, along with giving mint permission to the token manager (token manager address can be predicted via this query).

What's Changed

feat: added new token managers that have the mint/burn permissions by @Foivos in 023083e

Full Changelog: v1.2.1...v1.2.4