ivan-demchenko / roc-vscode-unofficial Goto Github PK

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid tarballDir option.

The tarballDir option option, if defined, must be a String.

Your configuration for the tarballDir option is false.

Good luck with your project ✨

Your semantic-release bot 📦🚀

Thanks for making this!

This is just a feature idea: format on save would be cool.

This is a minor issue but it would be nice to have.

The keyword interface is missing from the syntax here. I can submit a PR if you like.

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can fix this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

Invalid ovsx personal access token. Additional information:

Error: Command failed with exit code 1: ovsx verify-pat
❌ Namespace not found: IvanDemchenko

Unfortunately this error doesn't have any additional information. Feel free to kindly ask the author of the semantic-release-vsce plugin to add more helpful information.

Good luck with your project ✨

Your semantic-release bot 📦🚀

It would be great if the extension would be available on https://open-vsx.org as well. It would benefit users which are using VS Code alternatives (Codium, Theia).

Instructions to get started: https://github.com/eclipse/openvsx/wiki/Publishing-Extensions

I hit the following error:

Client roc-lang: connection to server is erroring.
Header must provide a Content-Length property.
{"{\"jsonrpc\"":"\"2.0\",\"result\":{\"data\":[0,[...],0]},\"id\":1}Content-Length: 38"}
Shutting down server.

Solution

I was able to fix it by updating to the latest vscode

If I use a " inside a """....""" block the string highlighting color stops, instead it should continue.