bytecodealliance / bytecodealliance/StarlingMonkey

Automate releases of the VSCode debugging extension

Open
#265 1 comment 0 reactions 0 assignees View on GitHub
enhancement help wanted
Dominant language
C
Stars
288
Forks
57
PR merge metrics
No merged PRs in 30d

Description

Now that #248 has landed, we should ideally automate releasing the extension from GH Actions.

One interesting aspect of that is how to do versioning. My instinct is that we shouldn't tie extension versions to StarlingMonkey's, because while the extension will have to be adapted to changes in StarlingMonkey at times, I would expect it to evolve at its own pace, gaining features and bug fixes independently from StarlingMonkey itself.

Marking this as `help wanted` because I don't plan on working on this myself for the time being, and would be grateful if someone else picked it up.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.