Release Candidate v2.0#551
Conversation
|
🚧 Release candidate build based on e3e7031 (potential merge of 21a0dfb). Assets can be found in the |
Mostly bringing in potentially relevant fixes from upstream (most notably Electron and maplibre-gl)
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
/build-rc |
|
🚧 Release candidate build based on e73eccb (potential merge of f5f9fb6). Assets can be found in the |
Follow up to #536 to make the back button in the settings subpages navigation functional.
Notable changes: - updates npm version to 11.2.1
Removes surfaced information about project stats sharing, since there aren't any settings for actually configuring it yet.
|
/build-rc |
|
🚧 Release candidate build based on 62b2165 (potential merge of 85e6fed). Assets can be found in the |
|
/build-rc |
|
🚧 Release candidate build based on 2e41ff2 (potential merge of 3abd0e3). Assets can be found in the |
By default, Electron allows running multiple instances of an application at the same time. This isn't useful in our case and also introduces a source of issues related to attempting to read/write from the same files. This was most notable on Windows, where the issue could be reproduced by doing the following: 1. Install and start application 2. In the Windows start menu, search and select the application to "open" it 3. See multiple instances of the app running. Now we only allow a single instance of the app to run. If there's an attempt to open another instance, we instead restore and focus the already open instance. The exception to this is when running the e2e tests, which makes use of multiple instances to enable parallel testing.
|
/build-rc |
|
🚧 Release candidate build based on e324b69 (potential merge of 9042ce2). Assets can be found in the |
|
🚀 A draft release pointing to 9321fed has been created at EDIT: First release workflow attempt failed and I re-ran the entire workflow without deleting the draft release the failed workflow created. Resulted in another release draft being created but not used. This comment was pointing at the new draft release but the artifacts were uploaded to the first one, so I updated the linked draft release to the first one instead. - Andrew |
This PR tracks QA of the release candidate for v2.0.
🍒 All changes to this branch should be cherry-picked from
main.🧪 Create a new Release Candidate build by commenting on this PR with the
/build-rccommand.🚧 An initial Release Candidate build will be triggered shortly, and the build URL will be posted here.
🚀 Merging this PR will trigger a release build.