Breaking database change gives success in technical validation

Hello,

Recently we added a new key to an existing database table as follows:

key(Key4; uniquefield)
{
       Unique = true;
}

This field was already present in the table (also already present without being a key in appsource).

We have a technical validation pipeline setup that uses the Run-AlValidation command from the BcContainerHelper (GitHub - microsoft/navcontainerhelper: Official Microsoft repository for BcContainerHelper, a PowerShell module, which makes it easier to work with Business Central Containers on Docker.). This checks our latest changes against the version of our app we have on AppSource.

This validation succeeded. However when updating the extension on a environment where there was already data in this table, the installation failed (which is logical). Are we doing something wrong in our valiation process that it did not see this as a red flag? Or is this a bug in BcContainerHelper? Or would this also pass through AppSource Validation without errors?