release: 4.9.0

[jsjoeio]

Published as a release candidate which can be installed via:

curl -fsSL https://code-server.dev/install.sh | sh -s -- --edge --standalone

[github-actions]

✨ code-server dev build published to npm for PR #5772!

• Last publish status: success
• Commit: 99033dd

To install in a local project, run:

npm install @coder/code-server-pr@5772

To install globally, run:

npm install -g @coder/code-server-pr@5772

[codecov]

Codecov Report

Merging #5772 (99033dd) into main (df49838) will increase coverage by 2.27%.
The diff coverage is 40.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #5772      +/-   ##
==========================================
+ Coverage   72.66%   74.94%   +2.27%     
==========================================
  Files          30       30              
  Lines        1683     1688       +5     
  Branches      370      371       +1     
==========================================
+ Hits         1223     1265      +42     
+ Misses        397      361      -36     
+ Partials       63       62       -1     

Impacted Files	Coverage Δ
src/node/routes/index.ts	78.64% <25.00%> (-2.17%)	⬇️
src/node/wrapper.ts	25.62% <100.00%> (+25.62%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f43082e...99033dd. Read the comment docs.

[jsjoeio]

Terminal is not working as shared first here: #5769 (comment)

Need to fix this before releasing.

[jsjoeio]

Oddly enough...when I run yarn watch locally, the terminal is working 🤔

I'm going to test installing this via npm locally next.

[jsjoeio]

Works on npm too 🤔

Maybe it's only affecting the non-npm builds? I'll try creating a standalone release locally.

[jsjoeio]

How I'm testing standalone release:

1. download npm artifact into code-server repo locally (on main branch) from here
2. unzip
3. run yarn release:standalone
4. run node ./release-standalone --port 3000

Still same result 🤔

Last thing I'll do is try running the yarn package step and testing the macOS package to see if that has any differences.

[jsjoeio]

Tested with yarn package like so:

1. VERSION="4.9.0-joe" yarn package
2. tar -xzf ./release-packages/code-server-4.9.0-joe-macos-amd64.tar.gz
3. node ./code-server-4.9.0-joe-macos-amd64 --port 3000

And still no issues 🤔

Only other thing that comes to mind is creating a draft release which will build artifacts in CI, then I can download them and test those (in case something in CI is being funky).

[jsjoeio]

Testing here: https://github.com/coder/code-server/actions/runs/3587010753

[jsjoeio]

Used the macos build from CI uploaded to draft release and still no issues 🤔

The last thing I can try is using a Linux build. I'll try that and report back.

[jsjoeio]

Hmm...I couldn't run code-server from in a Coder OSS workspace 🤔 I'm not sure why:

I think the next best option is to publish a release candidate 2 and have others test.

[jsjoeio]

see adobe/fetch#318 (comment)

[jsjoeio]

Release candidates have been tested and I've tested locally so I'm confident we can release this now. cc @code-asher

[jsjoeio]

Unrelated to release. Added to keep code coverage from decreasing and CI ✅

[code-asher]

LGTM after we export ChildProcess.