1.86.0.24036 - 14th Release - Linux, Windows, & MacOS

1.86.0

• Restored Ubuntu 18.04/Debian 9 Support
• Note: Dropped support for Ubuntu 16.04/Debian 8

1.85.2.24021 - 14th Release - Linux & Windows

• 1.85.2 minor update

(Still) TODO: Tweak default installer options, so that it doesn't try to register as a handler for all supported file types automatically.

1.85.1.24010 - 13th Release - Linux & Windows

• Rebase on upstream 1.85.1
• I was able to restore Windows 7/8/8.1 & Ubuntu 14.04/Debian 8 Support again! (Although it is getting harder and harder, with more files I have to modify, the further the version gets from 1.82.0, the last version officially shipped with Electron 22 and NodeJS 16.x)
• Still on Electron 22.3.27 because of the above, although I might move to https://github.com/win32ss/supermium-electron if it becomes stable.
• If I cant use the supermium-electron, I might build my own Electron (which I already have done to make AVX compiler optimized releases), with newer OpenSSL library and newer Node 16.x to increase security since it is kinda out of date. Normally I wouldn't worry about this in an Electron application, except that VSCode has open ports for debugging and it has active network connections to fetch announcements, help, and to install extensions.

TODO: Tweak default installer options, so that it doesn't try to register as a handler for all supported file types automatically.

UPDATE: I rebuilt the Linux releases, and so the version number is 24013 at the end. It was built with the exact same source code. The last two numbers only specify the day it was built. The reason is that some native modules are compiled against the system's libgcc. So it matters what Linux version you compile on. I originally compiled it on Ubuntu 22.04, but this means it wont run on anything older than 20.04. I forgot that I needed to compile it in my Ubuntu 18.04 Virtual Machine so that it will run correctly on 14.04/16.04 and Debian 8/9.

1.84.2.24001 - 12th Release - Linux & Windows

- Sadly, upstream vscode made some changes in 1.85.0 that use the native Nodejs fetch module, instead of the npm package node-fetch. This module is only available in Nodejs 17.5 and above. Since both the project, as well as Electron 22 use Node 16, I am making this the last Codium release with my custom nt6.patch patch to use Electron 22 and thus allow it to run on Windows NT 6.x.x systems (7/8/8.1). This change also means that it will no longer run on Debian 8 or Ubuntu 14.04. So....
(New) System Requirements: Windows 10 or later, Ubuntu 16.04 or later, Debian 9 or later, MacOS 10.14 or later.

HOWEVER there is a promising project called supermium-electron, and they already have a beta for Electron 28 running on Win 7 > https://github.com/win32ss/supermium-electron/releases/tag/v28-testing. If this project ever reaches stable status, I might re-add NT 6.x.x support. Also, if anyone wants to send in a patch via PR to revert back to using the node-fetch npm package, I could also do it that way.

UPDATE: Good news! I was able to get vscode working again on win 7! So this is not the last release for older oses like win7/8/8.1 and ubuntu 14.04/debian 8.

• Update to 1.84

• Fixed announcements to use my branding and to fetch announcements from my repo instead of Vscodium's (consequently you will see a warning about win7 with a link to these release notes). Also don't worry, any upstream VSCode or VSCodium announcements will still also be displayed.

1.83.1.23285 - 11th Release - Linux & Windows

• Rebase on 1.83.1
• Update Electron to 22.3.27 (Final Electron 22 release)

1.83.0.23279 - 10th Release - Linux & Windows

• Rebase on 1.83.0
• Merge branding patch
• Made nt_6.sh and nt6.patch to make building with Electron 22 simpler. You can make a build that does or does not support Win 7/8/8.1 & Ubuntu 16.04 by running that .sh file after ./get_repo.sh
• Update Electron to 22.3.26

I have decided that in the spirit of longevity and keeping Win7/8/8.1 alive, not only will I be basing Thorium-Win7 on Supermium M118, but I will be keeping all my Electron projects on Electron 22 indefinitely, until such time as there is a hard blocking reason why I can't anymore.

NOTE: The Windows 23283 versions are re-uploads because I needed to fix a compiler problem that made it where these binaries would only launch on Windows 8.1+ (Which is unacceptable since this fork is intended to run on Win7/8/8.1) Fixes #3

1.82.2.23266 - 9th Release - Linux & Windows

• Rebase on upstream 1.82.2
• Fixed some minor branding issues

1.82.1.23256 - 8th Release - Windows

• Update to 1.82.1 upstream
• Update Electron to 22.3.24
• Revert icons back to upstream

1.82.0.23255 - 7th Release - Linux & Windows

• This is based on 1.82.0.23255 except with the following modifications

• Downgraded from Electron 25 to Electron 22 to continue supporting Windows 7/8/8.1 and older Linux versions.

• Electron updated from 22.3.22 > 22.3.23

• 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.

1.81.2.23238 - 6th Release - Linux & Windows

• 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.