Resigning multiple PowerShell scripts with the same name replaces existing scripts

[AdmiringWorm]

Checklist

• [X] I confirm there are no unresolved issues reported on the Chocolatey Status page.
• [X] I have verified this is the correct repository for opening this issue.
• [X] I have verified no other issues exist related to my problem.
• [X] I have verified this is not an issue for a specific package.
• [X] I have verified this issue is not security related.
• [X] I confirm I am using official, and not unofficial, or modified, Chocolatey products.

What You Are Seeing?

When we are working on a project, and that project requires resigning of all the PowerShell scripts, if there are multiple PowerShell scripts that have the same name (like when there are multiple packages with an installation script), the functionality of copying the signed PowerShell script replaces any existing file with the same name, meaning only one of the expected files would be present.

This happens due to the same location being used for all of the scripts.

What is Expected?

Files that are different, but using the same name should not replace eachother. Optimally, we should preserve the directory structure from the root of the repository when copying files over.

We can then zip up the files created, to make it easier to update the files later.

How Did You Get This To Happen?

This was seen on an internal build where we resign files, no public reproduction steps are available.

System Details

• Chocolatey Recipe Version: 0.28.3

Installed Packages

N/A

Output Log

N/A

Additional Context

No response

[choco-bot]

:tada: This issue has been resolved in version 0.28.4 :tada:

The release is available on:

• GitHub Release
• NuGet Package

Your GitReleaseManager bot :package: :rocket: