New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vsce release v1.103.0 breaks attempting to build #7
Comments
Having the same issue. Very out of the blue. |
Whatever has happened has completely ruined my deployment process. What a shame. I had to re-write my simple deployment script to remove the dep on this action. Here's the commit for that: codefori/vscode-ibmi@0227b78 |
Same. To workaround it with minimal changes I downgraded/pinned
|
Actually just identified the issue and made a PR with a fix: #8. The problem is the underlying outdated Published a tag on my fork to do just that:
|
OK - I spoke too soon. Now I'm getting:
It appears this is a newish pending issue with |
Published tag
|
Interesting. Using Does |
Just pushed a 3.0.0 tag for this action that includes @sourishkrout's PR to update the dockerfile to node 16. Closing this for now. |
This fixes the broken nightly release. Breakage was caused by the new vsce release, and the fixed version requires a newer node version. The new lannonbr/vsce-action 3.0.0 includes the fix. lannonbr/vsce-action@0f3391e See github.com/lannonbr/vsce-action/issues/7 Change-Id: If8d1325bc17a5e89d02fe261b409b1dadde93a48 Reviewed-on: https://go-review.googlesource.com/c/vscode-go/+/361415 Trust: Hyang-Ah Hana Kim <hyangah@gmail.com> Run-TryBot: Hyang-Ah Hana Kim <hyangah@gmail.com> Reviewed-by: Suzy Mueller <suzmue@golang.org> TryBot-Result: kokoro <noreply+kokoro@google.com>
Starting with https://github.com/microsoft/vscode-vsce/releases/tag/v1.103.0 it appears npm is attempting to build keytar and fails due to lack of a build subsystem.
Has this been a problem before? Trying out workarounds but wanted to highlight the issue.
The text was updated successfully, but these errors were encountered: