[Bug]: Code-Server Version is still 4.4.0 after upgrading to 4.5.0

[balajib-b]

Is there an existing issue for this?

• I have searched the existing issues

OS/Web Information

• Web Browser: Chrome
• Local OS: Kubuntu 20.04
• Remote OS: Ubuntu 20.04
• Remote Architecture: arm64
• code-server --version:4.5.0

Steps to Reproduce

1. click menu
2. click Help
3. click About

Expected

version : 4.5.0

Actual

Version 4.4.0

Logs

No response

Screenshot/Video

Does this issue happen in VS Code or GitHub Codespaces?

• I cannot reproduce this in VS Code.
• I cannot reproduce this in GitHub Codespaces.

Are you accessing code-server over HTTPS?

• I am using HTTPS.

Notes

No response

[thediveo]

Confirming for arm64 .deb on Ubuntu 21.04 arm64: systemctl status code-server shows v4.5.0 in the logs, but even after clearing browser caches the web UI always shows v4.4.0 and the wrong commit hash.

[AalmanSadath]

Confirmed on Debian for arm64 and amd64 with individual .deb packages as well as using install script.

[GuillaumeLazar]

Same issue after upgrading from v4.4.0 to v4.5.0 using the install.sh script on Ubuntu 22.04 LTS (amd64).

$ dpkg -s code-server | grep Version
Version: 4.5.0

code-server "About popup" displays:

code-server: v4.4.0
Code: 1.68.1
Commit: 30d9c6cd9483b2cc586687151bcbcd635f373630

[LCMilstein]

Same issue trying multiple install approaches, including the GUI in Docker on Synology

[benz0li]

@jsjoeio Also reproducible at https://vscode-r.jupyter.b-data.ch with image R (base:test) + code-server as your account is still whitelisted.

JupyterLab > Terminal:

$ code-server --version
4.5.0 02b9d7ee856e31d9008d1ff24a175ff03b49010e with Code 1.68.1

code-server > Help > About:

[benz0li]

Cross reference: #5326

[somnisomni]

In released code-server-4.5.0-linux-amd64.tar.gz/lib/vscode/product.json, seems like some have-to-be-changed properties remain as same as v4.4.0 one.

[jsjoeio]

I see this as well. I think there was a "race condition" that happened with the 4.5.0 release. We normally create a branch called v4.5.0 for the release then tag it the same but GH added something that doesn't allow them to be the same anymore.

#5352 should

I'm testing right now before releasing 4.5.1 and still see this issue so we may need to fix this before releasing: