You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Code-Server Version is still 4.4.0 after upgrading to 4.5.0 #5316
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.
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.
Activity
thediveo commentedon Jul 3, 2022
Confirming for arm64 .deb on Ubuntu 21.04 arm64:
systemctl status code-servershows 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 commentedon Jul 3, 2022
Confirmed on Debian for arm64 and amd64 with individual .deb packages as well as using install script.
GuillaumeLazar commentedon Jul 6, 2022
Same issue after upgrading from v4.4.0 to v4.5.0 using the
install.shscript on Ubuntu 22.04 LTS (amd64).$ dpkg -s code-server | grep Version Version: 4.5.0code-server "About popup" displays:
LCMilstein commentedon Jul 6, 2022
Same issue trying multiple install approaches, including the GUI in Docker on Synology
benz0li commentedon Jul 8, 2022
@jsjoeio Also reproducible at https://vscode-r.jupyter.b-data.ch with image
R (base:test) + code-serveras your account is still whitelisted.JupyterLab > Terminal:
code-server > Help > About:
benz0li commentedon Jul 8, 2022
Cross reference: #5326
somnisomni commentedon Jul 16, 2022
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 commentedon Jul 18, 2022
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.0for 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:
fix(ci): add package.json.version to code cachekey
jsjoeio commentedon Jul 19, 2022
We think this is because CI hit the cache when releasing 4.5.0 so it didn't rebuild leading to this issue.
I will test, verify and then close if it fixes it.
See 3cd3475
jsjoeio commentedon Jul 19, 2022
fixed via 3cd3475
This will be updated in the next release.
release: 4.5.1 (#5354)