Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Synchronize releases with VSCode

Open
#7,094 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
vscode
Domain
release

Research direction

Start by reviewing the current code-server release process and how VSCode releases are tracked. Define the expected update timing relative to each VSCode release, then document and commit to the resulting SLA so the release timing is clear to customers.

Written by the indexing model from the issue text.

Description

enhancement

What is your suggestion?

Synchronize code-server releases with VSCode releases. As soon as the latest VSCode is released, I expect code-server to be updated.

Why do you want this feature?

Coming from enterprise customer feedback in Coder.

While the upgrade speed of code-server is relatively fast, customers often file requests an update before we publish. Local developers can upgrade to the latest VSCode as soon as the changelog is released, but code-server users must wait on us.

Customers have often noted dissatisfaction with this delayed time to promote. To prevent the wait time and reduce tickets filed both by developers in our customers' organizations and from our customers to us, we should be proactive about upgrading as soon as the newest VSCode is available. Closing this issue means documenting and committing to an SLA on code-server update timing.

Are there any workarounds to get this functionality today?

By waiting for the code-server update to happen, trailing slightly behind VSCode.

Dominant language
TypeScript
Stars
79.4k
Forks
6.9k
Avg merge
2d 13h
Merged PRs (30d)
39

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/code-server

All issues in coder/code-server

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.