Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/cache@v4, actions/github-script@v7. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

The InstallExecuteSequence table contains an action 'RemoveShortcuts' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\PythonEc64bitMM.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module.

The InstallExecuteSequence table contains an action 'RemoveShortcuts' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\PerlEc64bitMM.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module.

The CustomAction table contains a row with primary key(s) 'ExecSecureObjectsRollback_64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.

The CustomAction table contains a row with primary key(s) 'ExecSecureObjects_64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.

The CustomAction table contains a row with primary key(s) 'SchedSecureObjectsRollback_x64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.

The CustomAction table contains a row with primary key(s) 'SchedSecureObjects_x64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This is likely due to collision of rows with the same primary key(s) (but other different values in other columns) between the database and the merge module.

The InstallExecuteSequence table contains an action 'SchedSecureObjects_x64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module.

The InstallExecuteSequence table contains an action 'SchedSecureObjectsRollback_x64' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module.

The InstallExecuteSequence table contains an action 'RemoveShortcuts' which cannot be merged from the merge module '..\..\packages\encoding-converters-core\0.9.8\runtimes\EcDistFiles\MergeModules\x64\Release\EC_40_64bit_MM.msm'. This action is likely colliding with an action in the database that is being created. The colliding action may have been authored in the database or merged in from another merge module. If this is a standard action, it is likely colliding due to a difference in the condition for the action in the database and merge module. If this is a custom action, it should only be declared in the database or one merge module.