HaaLeo / publish-vscode-extension

GitHub action to publish your VS Code Extension to the Open VSX Registry or Visual Studio Marketplace.
MIT License
209 stars 13 forks source link

missing published extension #29

Closed daiyam closed 1 year ago

daiyam commented 2 years ago
publish-vscode-extension Version Operating System
v1.1.0 Ubuntu 20.04.5 LTS

Description

Hi Leo,

I can't publish my extension to OpenVSX. I'm not sure if it's an issue with your extension or OpenVSX.

The publishing was successful but the extension is missing on OpenVSX.

##[debug]Evaluating condition for step: 'Publish to Open VSX Registry'
##[debug]Evaluating: success()
##[debug]Evaluating success:
##[debug]=> true
##[debug]Result: true
##[debug]Starting: Publish to Open VSX Registry
##[debug]Loading inputs
##[debug]Evaluating: secrets.OPEN_VSX_TOKEN
##[debug]Evaluating Index:
##[debug]..Evaluating secrets:
##[debug]..=> Object
##[debug]..Evaluating String:
##[debug]..=> 'OPEN_VSX_TOKEN'
##[debug]=> '***'
##[debug]Result: '***'
##[debug]Loading env
Run HaaLeo/publish-vscode-extension@v1
Specifically, running GitHub Action HaaLeo/publish-vscode-extension@v1.1.0.
##[debug]Start action with options="{"pat":"***","registryUrl":"https://open-vsx.org","packagePath":"./","yarn":false,"dryRun":false,"noVerify":false,"preRelease":false}".
::group::Package the Extension
Package the Extension
::group::Publish the Extension
Publish the Extension
  ::endgroup::
##[debug]Node Action run completed with exit code 0
##[debug]Set output vsixPath = explicit-folding-0.23.0.vsix
##[debug]Finishing: Publish to Open VSX Registry

Is it possible to output the logs of the command?

daiyam commented 2 years ago

I was able to publish the extension and I did get the log:

🚀 Published zokugun.explicit-folding v0.23.1

I just wonder why the action didn't fail if there were a error somewhere...

HaaLeo commented 2 years ago

Hi @daiyam thx for reporting this bug. The action should definitely fail when errors occur.

Without being able to reproduce the behavior consistently this will be hard to debug. Can you reproduce this one or it just went away the next try?

daiyam commented 2 years ago

I tried to publish my extension v0.23.0 3 times:

So I can't reproduce the error. Sorry. But I don't think the issue is due to your extension. You might just want to capture the output and verify if it match the expect output...

jeronimoek commented 1 year ago

The same happens to me, the ovsx CLI output is a success message, but no new version is published, so I guess the issue lies in their CLI

jeronimoek commented 1 year ago

My output:

Run HaaLeo/publish-vscode-extension@v1
  with:
    pat: ***
    extensionFile: color-picker-universal.vsix
    registryUrl: https://open-vsx.org
    packagePath: ./
    yarn: false
    dryRun: false
    noVerify: false
    preRelease: false
Specifically, running GitHub Action HaaLeo/publish-vscode-extension@v1.2.0.
Package the Extension
  The extension was already packaged. Skip packaging.
Publish the Extension
  🚀  Published JeronimoEkerdt.color-picker-universal v1.7.1

but as you can see here https://open-vsx.org/extension/JeronimoEkerdt/color-picker-universal/ there is no version 1.7.1 published

I just saw this project uses ovsx@0.7.1. There is version 0.8.0 available, maybe that helps (just guessing)

jeronimoek commented 1 year ago

Never mind, I just checked again, and after 1 hour approx. the extension was suddenly published. Looks like ovsx servers are struggling

HaaLeo commented 1 year ago

As it seems to be an upstream issue I will mark it as "wontfix". If you find any hints which suggest this is a problem of this action feel free to reopen this issue.