I have files as part of my build that include the @ symbol.
For example: “images\findbarButtonemail@example.com”.
When OctoPack runs it creates the nupkg but the files within the nupkg seem to be URL encoded (the file is now: images/findbarButton-next%402x.png"). When leveraging them against Octopus Deploy directly it seems to translate back out during the deployment process fine. However, we also use those same packages to create offline installers (not handled by OctopusDeploy) and extracting these archives means that the file names are incorrect.
Is this a bug in OctoPack or any configuration parameter we can add to prevent the encoding of filenames like that?