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
If we try and publish to multiple places, with a set target:
- name: Publish to Open VSX Registryuses: HaaLeo/publish-vscode-extension@v1id: publishToOpenVSXwith:
pat: ${{ secrets.OPEN_VSX_TOKEN }}target: ${{matrix.os}}
- name: Publish to Visual Studio Marketplaceuses: HaaLeo/publish-vscode-extension@v1with:
pat: ${{ secrets.VS_MARKETPLACE_TOKEN }}registryUrl: https://marketplace.visualstudio.comtarget: ${{matrix.os}}extensionFile: ${{ steps.publishToOpenVSX.outputs.vsixPath }}
we get
Error: Both options not supported simultaneously: 'packagePath' and 'target'. Use 'vsce package --target <target>' to first create a platform specific package, then use 'vsce publish --packagePath <path>' to publish it.
on the second action. If we remove the extensionFile field, it still produces this error.
If we remove the target field, it turns out the vsixPath output of the first action will extensionname-X.X.X.vsix, even though target is set. This means the second action will upload it as universal.
Expected Behavior
We should either be able to set target on both actions, or when the action produces a vsix with a specific target, it should name it according to how vsce package names it, so it gets uploaded correctly in the second action, i.e. extensionname-platform-X.X.X.vsix
Actual Behavior
See description
Steps to Reproduce
Create an action as mentioned in description
run it
try removing the target or extension file field from the 2nd invocation of the action
Context
The text was updated successfully, but these errors were encountered:
Description
If we try and publish to multiple places, with a set target:
we get
on the second action. If we remove the extensionFile field, it still produces this error.
If we remove the target field, it turns out the vsixPath output of the first action will
extensionname-X.X.X.vsix
, even though target is set. This means the second action will upload it as universal.Expected Behavior
We should either be able to set target on both actions, or when the action produces a vsix with a specific target, it should name it according to how
vsce package
names it, so it gets uploaded correctly in the second action, i.e.extensionname-platform-X.X.X.vsix
Actual Behavior
See description
Steps to Reproduce
Context
The text was updated successfully, but these errors were encountered: