Skip to content

Automate releases of the VSCode debugging extension #265

Open

Description

@tschneidereit

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.

Activity

  1. squillace commented on Aug 16, 2025

    @squillace

    I agree, we would want versioning to be independent of SM. I note we haven't pushed this yet; I'm building and testing this weekend.

    Project Details
    BytecodeAlliance/StarlingMonkey
    https://github.com/BytecodeAlliance/StarlingMonkey/commits
    10 Pull Requests
    55 Open Issues
    More Info
    Version 0.1.2

    Released on 3/28/2025, 9:35:06 AM
    Last updated
    3/28/2025, 11:09:33 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions