Skip to content

Add pre-release action#254

Merged
will-v-pi merged 1 commit intomainfrom
pre-release-action
Mar 10, 2026
Merged

Add pre-release action#254
will-v-pi merged 1 commit intomainfrom
pre-release-action

Conversation

@will-v-pi
Copy link
Collaborator

Add a workflow to do pre-releases (using patch version, as VS Code only supports x.x.x versions)

Pre-releases can now be done by dispatching the Pre-release workflow, which will do a patch release and publish the debug version of the extension

Main releases still need to be done as before, and should be limited to major/minor versions to avoid confusion (ie anything that isn't x.x.0 is a pre-release)

@will-v-pi will-v-pi requested a review from paulober February 5, 2026 17:00
@will-v-pi will-v-pi merged commit 1474518 into main Mar 10, 2026
2 checks passed
@paulober paulober deleted the pre-release-action branch March 10, 2026 22:29
@paulober
Copy link
Collaborator

Hi @will-v-pi, good idea! Sorry for the late response — I completely missed this during my exam period.

LGTM👍

One small thing I noticed: detecting pre-releases via string matching on "Pre-release" in the commit message is a bit fragile. If the commit message changes slightly or the workflow is triggered by a different event, the logic might behave differently than expected.

In the long run it might be more robust to base this on tags or some explicit signal in the workflow, but for now it should work fine.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants