copy package.json to staging directory

[danfiedler-msft]

No description provided.

[gfs]

I don't think this is the correct approach. The package.json is required as a component of the vsix and should be read out of it. I think the error actually means that it isn't finding the vsix to publish.

Additionally, we've found that its necessary to manually mark pre-release versions with vsce with a special flag, or else they will clobber all stable release versions.

See

DevSkim/Pipelines/vscode/devskim-vscode-release.yml

Lines 204 to 219 in bd092d9

	- task: PowerShell@2
	displayName: Publish Pre-Release / Release
	inputs:
	targetType: 'inline'
	script: |
	$packPath = Resolve-Path $env:BUILD_STAGINGDIRECTORY\*.vsix
	if ("$(ReleaseVersion)".Contains("-"))
	{
	echo "Publishing as --pre-release = $(ReleaseVersion)"
	vsce publish --packagePath $packPath --pat $(VS_Token) --pre-release
	}
	else
	{
	echo "Publishing as official release = $(ReleaseVersion)"
	vsce publish --packagePath $packPath --pat $(VS_Token)
	}

for previous publish action using package path and switching on release/pre-release.

[danfiedler-msft]

I don't think this is the correct approach. The package.json is required as a component of the vsix and should be read out of it. I think the error actually means that it isn't finding the vsix to publish.

Updated the publish step to bring back release vs. prerelease. Added a step to list the contents of the staging directory.

I know from the signing step the VSIX exists prior to the move from binaries to staging.

Signed file: D:\a_work\1\b\Unsigned_Plugin\vscode-devskim-1.0.45.vsix

I think the move should work so it will be surprising if the VSIX isn't in the expected spot for publishing.