I am not sure why this happens but when I run the command
$newPackage = Add-DBOBuild -Path $package -ScriptPath $sqlPathItems -Build 5.4 -Type Unique, New, Modified
The new build has many of the same files as the last existing build in the package (5.3).
For example, if I look in the dbops.package.json, build 5.3 has a file like this one
{
"PackagePath": "90 - Scripts/abc.sql",
"Hash": "0x1B5018D66760F9053685CC3CFE5FD23C"
}
and build 5.4 will also have it with the same path and hash....
Build 5.2 has all the files
Build 5.3 seems to have only the new and modified ones since 5.2 which is ok
Build 5.4 has 90% the same files as 5.3 with same hash and files were not updated at all.
I am not sure why this happens but when I run the command $newPackage = Add-DBOBuild -Path $package -ScriptPath $sqlPathItems -Build 5.4 -Type Unique, New, Modified
The new build has many of the same files as the last existing build in the package (5.3). For example, if I look in the dbops.package.json, build 5.3 has a file like this one { "PackagePath": "90 - Scripts/abc.sql", "Hash": "0x1B5018D66760F9053685CC3CFE5FD23C" } and build 5.4 will also have it with the same path and hash....
Build 5.2 has all the files Build 5.3 seems to have only the new and modified ones since 5.2 which is ok Build 5.4 has 90% the same files as 5.3 with same hash and files were not updated at all.