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
The VS Code extension is currently published under my personal account. Since several other people have worked on the project since (and will start working on it shortly), we should choose a more neutral publisher instead.
Desired solution
Add more metadata like
an image,
galleryBanner.color,
link to the documentation.
Reset the version to 0.1.0. We bumped the version to 1.0.0 so the DSL Jar (which is quite stable) could be published to Maven Central to be consumed by the API-Editor. It was a mistake, however, to also set the version of the VS Code extension to 1.0.0. This is an opportunity to fix this.
Build the VSIX archive and publish it under the Safe-DS publisher.
Is your feature request related to a problem?
The VS Code extension is currently published under my personal account. Since several other people have worked on the project since (and will start working on it shortly), we should choose a more neutral publisher instead.
Desired solution
galleryBanner.color
,0.1.0
. We bumped the version to1.0.0
so the DSL Jar (which is quite stable) could be published to Maven Central to be consumed by the API-Editor. It was a mistake, however, to also set the version of the VS Code extension to1.0.0
. This is an opportunity to fix this.Possible alternatives (optional)
No response
Screenshots (optional)
No response
Additional Context (optional)
This will also unblock #441.
The text was updated successfully, but these errors were encountered: