You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, if there's a "+" sign in any file that's added as an asset (for example ".github/workflows/node-4+.yml" in some node packages) this will break the VSIX extensions (at least for Azure DevOps Server 2019) since the path of the file is added as the asset type for each file in the extension.vsixmanifest manifest-file and a "+" sign is not allowed in there according to Azure DevOps Server 2019. A thus with this node module created VSIX package will not be installable if it uses a file that has a "+" sign in it. Please add code that would handle characters in file names which wouldn't be allowed in the asset type.
This extension is effected for example: https://github.com/dependency-check/azuredevops/ through the node modules "resolve" and "is-core-module"
The text was updated successfully, but these errors were encountered:
Hi, if there's a "+" sign in any file that's added as an asset (for example ".github/workflows/node-4+.yml" in some node packages) this will break the VSIX extensions (at least for Azure DevOps Server 2019) since the path of the file is added as the asset type for each file in the extension.vsixmanifest manifest-file and a "+" sign is not allowed in there according to Azure DevOps Server 2019. A thus with this node module created VSIX package will not be installable if it uses a file that has a "+" sign in it. Please add code that would handle characters in file names which wouldn't be allowed in the asset type.
This extension is effected for example: https://github.com/dependency-check/azuredevops/ through the node modules "resolve" and "is-core-module"
The text was updated successfully, but these errors were encountered: