Using extensionFile option throws error about publish-vscode-extension HOT 2 CLOSED

Hi @hybras, thank you for your contribution. Let me break this issue down:

Cause

This issue occurs since the default value for packagePath is ./. Now in the workflow you additionally specify extensionFile: rust-analyzer.vsix → Both options are defined → Error: Please specify either an extension file or a package path, but not both..

You can see this also in the unfolded action log:

Solution

Similar to the second example in the README you must manually unset the packagePath option. I admit that this is probably somewhat unintuitive and in future releases I may reconsider this behaviour. However, for now the following snippet should solve your issue:

    - name: "Publish to Open VSX Registry"
      uses: HaaLeo/publish-vscode-extension@v0
      with:
        pat: ${{ secrets.OPEN_VSX_TOKEN }}
        extensionFile: "rust-analyzer.vsix"
        packagePath: ""

If you still experience any issues do not hesitate to file another issue.

from publish-vscode-extension.

I unset packagePath as you suggested. It worked like a charm. If your into rust, check out the latest release of rust-analyzer.

Thank you for your help, your gh action is invaluable.

from publish-vscode-extension.