Skip to content

1.81.2.23238 - 6th Release - Linux & Windows
Compare
Choose a tag to compare
@Alex313031 Alex313031 released this 26 Aug 21:44
· 280 commits to master since this release
1.81.1.23238
6651125
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

  • This is based on 1.81.1.23238 except with the following modifications

  • Electron updated from 22.3.18 > 22.3.22

  • Yarn was not run with --frozen-lockfile, so there might be slightly updated versions of packages compared to upstream.

  • The .zips have been made truly portable by automatically including a 'data' dir, so that when you run it, your user profile/settings are stored in that folder.

  • @vscode/gulp-electron was migrated to my fork with an updated rcedit, to fix a very pesky bug where the icon and metadata was not set on the main executable correctly.
    I filed bugs on this at VSCodium > VSCodium#1571, and at upstream VSCode > microsoft/vscode#191077

I also filed an issue with the vscode-gulp-electron package source, and made a pull request with the fix > microsoft/vscode-gulp-electron#17.

Unfortunately, they are being some sort of way. I don't know if I upset them somehow, or they are being obstinate, but they closed my issue, removed the ability to create issues in that repo for everyone, and then closed my VSCode issue with no explanation. This icon issue is very real, you can build two identical vscode, except make one use the gulp-electron package with the fixed/updated rcedit, and you can see that both will
build and run, but one will have the correct icon, and the other will have the incorrect default Electron icon and metadata (version, copyright, etc.) set incorrectly.

  • Entire repo was rebased on top of the latest VSCodium, and I made some more fixes to my build scripts. If you want to build for yourself, simply run ./get_repo.sh and then ./build.sh from within the root of the repo.

So, I incremented the version number, however, the tag for this release will still be 1.81.1, in the case that they release an actual 1.81.2 upstream.
The 1.81.x.x branch is the last branch to support Windows 7/8/8.1 since they moved to Electron 25 in VSCode 1.82.0. When 1.82.x becomes stable, I will make a build of the last commit of the 1.81 branch, make sure the Electron in it is updated to the last 22 version, and publish that as a special release for those OSes.

[UPDATE]: Reverting VSCode to use Electron 22 again is a simple task, so I will continue to make builds based on Electron 22 until january of next year.

Assets 7
Loading