Skip to content

Conversation

@benz0li
Copy link
Contributor

@benz0li benz0li commented Feb 11, 2026

Ping @code-asher

Please release v4.109.0 first. Thank you.

@benz0li benz0li requested a review from a team as a code owner February 11, 2026 05:37
@Delta1977
Copy link

@benz0li @code-asher
is the merge and release-process a "one man show"?
as i see
Update 1.109.1: The update addresses these security issues.

Update 1.109.2: The update addresses these issues

why are we on 1.108.x?

@code-asher
Copy link
Member

I just released the RC for 4.109.0 so I will promote it tomorrow assuming no one reports issues and then release 4.109.2 right after that.

is the merge and release-process a "one man show"?

Yeah I have to manually trigger all the releases, and it is janky because I have to wait until the build in CI finishes after merging which takes 50+ minutes and sometimes I forget to come back and make the release...

This last release is particularly delayed because I have been on vacation (actually I still am, for another few weeks).

I really would like to completely redo the release process and make it so I just have to tag a commit and the rest is handled automatically, or even make it automatically release when a VS Code update is merged in, but I have not had the time.

@code-asher code-asher merged commit 9184b64 into coder:main Feb 11, 2026
10 checks passed
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.

3 participants