-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump Brave's Windows updater (Omaha) to v1.3.361.113 #22060
Bump Brave's Windows updater (Omaha) to v1.3.361.113 #22060
Comments
Re-opening as I've had to roll back #12868 in brave/brave-core#12874. |
@brave/legacy_qa we should check Win 10 and 11 at a minimum. Win 8 and 7 would be helpful, but not strictly necessary. Update - based on further discussions, we're going to execute full checks on Win 10 and 11 x64. We're going to do targeted cases on Win 8 x86, Win 7, Win 10 x86. |
Verification PASSED on
Windows 10 x641. Verify installers and auto-updater work on a clean profile Case 1: Verify the Omaha updater version when 1.39.x is installed_PASSEDPre-requisites:
Steps:
Case 2: Download and install stub installer binary 1.39.x with Admin rights_PASSED
Case 3: Download and install standalone silent installer binary 1.39.x_PASSED
2. Verify installers and auto-updater works on upgrade profile Case 1:Verify the Omaha updater version in an upgraded profile (Install 1.34.60 ->upgrade to 1.39.x)_PASSEDSteps :
Followed the steps from "Background updates" in brave/brave-core#11096 - to verify the Omaha updates silently in the background and confirmed that updater got updated to latest version Case 2: Install standalone installer 1.38.x and upgrade the profile to 1.39.x_PASSED
Case 3: Install standalone installer 1.38.x and upgrade the profile to 1.39.x test channel_PASSED
Case 4: Install standalone silent installer 1.38.x and upgrade the profile to 1.39.x_PASSED
3. Verify installers and auto-updater work when the user declines the Admin rights in UAC [Note : when brave is installed for the current user (without admin rights) the Case 1: Verify standalone installer can be installed without admin rights and updater works_PASSED
Case 2: Verify stub installer can be installed without admin rights_PASSED
4. Verify re-install same installer version works Case 1: Verify standalone installer can be installed twice and update works_PASSED
Case 2: Verify stub installer can be installed twice_PASSED
Case 3: Verify standalone silent installer can be installed twice and update works_PASSED
5. Install quite older installers and check update works correctly Case 1: Install 1.30.x and ensure upgrade works_PASSED
Case 2: Install 1.34.x and ensure upgrade works_PASSED
Case 3: Install 1.29.x and ensure upgrade works_PASSED
Case 4: Install 1.22.x and ensure upgrade works_PASSED
Case 5: Install 1.18.x and ensure upgrade works_PASSED
6. Verify that install brave works when the Internet is disconnected Case 1: Verify standalone installer can be installed when the network is disconnected_PASSED
Case 2: Verify standalone silent installer can be installed when the network is disconnected_PASSED
Case 3: Verify stub installer can't be installed when the network is disconnected_PASSED
7. Verify installing a new binary by older binary from different installers (e.g one is standalone and the other is stub/silent) Case 1: Install standalone installer 1.38.x and upgrade it by 1.39.x stub installer_PASSED
Case 2: Install standalone silent installer 1.38.x and upgrade it by 1.39.x stub installer(decline Admin rights)_PASSED
Case 3: Install standalone silent installer 1.38.x and then autoupgrade_PASSED
Case 4: Install standalone installer 1.38.x and then autoupgrade_PASSED
|
QA/Blocked until the clarification gets resolved brave/brave-core#12895 (comment) |
@mherrmann Could you review the scenario please?
@mherrmann Once the build is upgraded to |
@GeetaSarvadnya it might be OK. Do background updates update the updater to |
@mherrmann: I ran |
@GeetaSarvadnya this was my mistake. The new updater is not yet uploaded to the update server (otherwise, all users would already be receiving it). I've uploaded the new updater to the staging update server. You can configure your machine to pull updates from staging by setting the registry string value The above should let you update the updater to |
@mherrmann Brave background task scheduler update the Omaha updater to latest version |
Verification
Windows 11x641. Verify installers and auto-updater work on a clean profile Case 1: Verify the Omaha updater version when 1.39.x is installed_PASSEDPre-requisites:
Steps:
Case 2: Download and install stub installer binary 1.39.x with Admin rights_PASSED
Case 3: Download and install standalone silent installer binary 1.39.x with out Admin rights_PASSED
2. Verify installers and auto-updater works on upgrade profile Case 1:Verify the Omaha updater version in an upgraded profile (Install 1.34.60 ->upgrade to 1.39.x)_PASSEDSteps :
Updater Validation
Case 2: Install standalone installer 1.38.x and upgrade the profile to 1.40.x_PASSED
Case 3: Install standalone installer 1.38.x and upgrade the profile to 1.40.x test channel_PASSED
Case 4: Install standalone silent installer 1.38.x and upgrade the profile to 1.40.x_PASSED
3. Verify installers and auto-updater work when the user declines the Admin rights in UAC Case 1: Verify standalone installer can be installed without admin rights and updater works_PASSED
Case 2: Verify stub installer can be installed without admin rights_PASSED
4. Verify re-install same installer version works Case 1: Verify standalone installer can be installed twice and update works_PASSED
Case 2: Verify stub installer can be installed twice_PASSED
Case 3: Verify standalone silent installer can be installed twice and update works_PASSED
5. Install quite older installers and check update works correctly Case 1: Install 1.30.x and ensure upgrade works_PASSED
Case 2: Install 1.34.x and ensure upgrade works_PASSED
Case 3: Install 1.29.x and ensure upgrade works_PASSED
Case 4: Install 1.22.x and ensure upgrade works_PASSED
Case 5: Install 1.18.x and ensure upgrade works_PASSED
6. Verify that install brave works when the Internet is disconnected Case 1: Verify standalone installer can be installed when the network is disconnected_PASSED
Case 2: Verify standalone silent installer can be installed when the network is disconnected_PASSED
Case 3: Verify stub installer can't be installed when the network is disconnected_PASSED
7. Verify installing a new binary by older binary from different installers (e.g one is standalone and the other is stub/silent) Case 1: Install standalone installer 1.38.x and upgrade it by 1.39.x stub installer_PASSED
Case 2: Install standalone silent installer 1.38.x and upgrade it by 1.39.x stub installer(decline Admin rights)_PASSED
Case 3: Install standalone silent installer 1.38.x and then auto upgrade_PASSED
Case 4: Install standalone installer 1.38.x and then auto upgrade_PASSED
|
I took the staging update server |
@mherrmann we still have to test this issue with Win 11 (@MadhaviSeelam is doing) and Win 8 (@kjozwiak will do), so sounds like we might need that back. |
@LaurenWags I see. I'm bringing staging back online. |
Thanks @mherrmann - we should be able to get back to this once we get some other priorities completed. |
Verified with:
Windows 10 x861. Verify installers and auto-updater work on a clean profile Case 1: Verify the Omaha updater version when 1.39.x is installed - PASSEDPre-requisites:
Steps:
2. Verify installers and auto-updater works on upgrade profile Case 1:Verify the Omaha updater version in an upgraded profile (Install 1.37.77 ->upgrade to 1.39.x) - PASSEDSteps :
Worked with Geeta to understand and follow the steps from 1.) #22060 (comment) and then 2.) "Background updates" in brave/brave-core#11096 - to verify the Omaha updates silently in the background and confirmed that updater got updated to latest version Confirmed Omaha updater version updated from Case 2: Download and install stub installer binary 1.39.x with Admin rights - PASSED
Case 3: Download and install standalone silent installer binary 1.39.x - PASSED
3. Verify installers and auto-updater work when the user declines the Admin rights in UAC Case 1: Verify standalone installer can be installed without admin rights and updater works - PASSED
Installed 1.39.96 --> Updated to 1.39.106
4. Verify re-install same installer version works Case 1: Verify standalone installer can be installed twice and update works - PASSED
5. Install quite older installers and check update works correctly Case 1: Install 1.30.x and ensure upgrade works - PASSED
6. Verify that install brave works when the Internet is disconnected Case 1: Verify standalone installer can be installed when the network is disconnected - PASSED
7. Verify installing a new binary by older binary from different installers (e.g one is standalone and the other is stub/silent) Case 1: Install standalone installer 1.38.x and upgrade it by 1.39.x stub installer - PASSED
|
Verification passed on
Windows 7 x641. Verify installers and auto-updater work on a clean profile Case 2: Download and install stub installer binary 1.39.x with Admin rights_PASSED
2. Verify installers and auto-updater works on upgrade profile Case 2: Install standalone installer 1.38.x and upgrade the profile to 1.39.x_PASSED
3. Verify installers and auto-updater work when the user declines the Admin rights in UAC [Note : when brave is installed for the current user (without admin rights) the Case 2: Verify stub installer can be installed without admin rights_PASSED
4. Verify re-install same installer version works Case 1: Verify standalone installer can be installed twice and update works_PASSED
5. Install quite older installers and check update works correctly Case 1: Install 1.30.x and ensure upgrade works_PASSED
6. Verify that install brave works when the Internet is disconnected Case 1: Verify standalone installer can be installed when the network is disconnected_PASSED
7. Verify installing a new binary by older binary from different installers (e.g one is standalone and the other is stub/silent) Case 1: Install standalone installer 1.38.x and upgrade it by 1.39.x stub installer_PASSED
|
- Added Solana support for account creation, sending SOL and sending SPL tokens with Brave Wallet. ([#22348](brave/brave-browser#22348)) - Added the ability to buy with Ramp using Brave Wallet. ([#21639](brave/brave-browser#21639)) - Added JSONSanitizer to API helper requests for Brave Wallet. ([#21831](brave/brave-browser#21831)) - Added Dapp UI for requesting a public key and for decrypting ciphers using Brave Wallet. ([#21177](brave/brave-browser#21177)) - Added web3_clientVersion support for Brave Wallet. ([#19278](brave/brave-browser#19278)) - Added the ability to allow users to search sites for RSS feeds for Brave News. ([#21768](brave/brave-browser#21768)) - Added support for blob partitioning. ([#21746](brave/brave-browser#21746)) - Added minimum macOS version for Sparkle update process. ([#22918](brave/brave-browser#22918)) - [Security] Blocked "window.ethereum" completely in third party iframes. ([#22686](brave/brave-browser#22686)) - [Security] Updated Brave Wallet panel to prominently display eTLD+1 as reported on HackerOne by renekroka. ([#21787](brave/brave-browser#21787)) - [Security] Fixed incorrect origin being displayed in Brave Wallet when a spend approval is pending. ([#19557](brave/brave-browser#19557)) - Implemented eth_getEncryptionPublicKey for Brave Wallet. ([#19276](brave/brave-browser#19276)) - Implemented account discovery when restoring Brave Wallet. ([#18104](brave/brave-browser#18104)) - Updated Omaha installer version for Windows to v1.3.36.113. ([#22060](brave/brave-browser#22060)) - Updated default IPFS configuration values. ([#22068](brave/brave-browser#22068)) - Updated Gas Limit validation and error messaging for unapproved transactions with Brave Wallet. ([#21714](brave/brave-browser#21714)) - Updated Brave Wallet to automatically add swap taker asset to the visible asset list. ([#21428](brave/brave-browser#21428)) - Updated Brave Wallet portfolio network filter for multichain support. ([#20780](brave/brave-browser#20780)) - Reduced adblock filter memory usage by optimizing unused regex rules. ([#21970](brave/brave-browser#21970)) - Removed known Dialog Insight user tracking parameters from URLs. ([#22082](brave/brave-browser#22082)) - Removed ability to swap ERC721 tokens with Brave Wallet. ([#21550](brave/brave-browser#21550)) - Fixed crash which occurred when opening Brave Shields while using Google Meet. ([#22814](brave/brave-browser#22814)) - Fixed inability to rename Solana account in Brave Wallet after it has been created. ([#22958](brave/brave-browser#22958)) - Fixed incorrectly computed insufficient funds errors in Brave Wallet. ([#22877](brave/brave-browser#22877)) - Fixed ERC20 and ERC721 transfers being incorrectly displayed as ETH transfers in the Brave Wallet transactions panel. ([#22044](brave/brave-browser#22044)) - Fixed text alignment issues under the Brave Wallet "Recent transactions" panel when using long account names. ([#21216](brave/brave-browser#21216)) - Fixed breakage in webpack build caused by OpenSSL 3.0. ([#22305](brave/brave-browser#22305)) - Fixed two windows being opened on launch when the browser was installed without administrator privileges on Windows. ([#22179](brave/brave-browser#22179)) - Upgraded Chromium to 102.0.5005.61. ([#22923](brave/brave-browser#22923)) ([Changelog for 102.0.5005.61](https://chromium.googlesource.com/chromium/src/+log/101.0.4951.67..102.0.5005.61?pretty=fuller&n=1000))
Description
We want to disable some statistics collection in Brave's auto-updater on Windows. We're taking this as an opportunity to make a few other small improvements to the auto-updater. Specifically:
This issue should count as resolved once stats collection no longer occurs as described in brave/omaha#41 and most of Brave's auto-update fleet on Windows uses the new updater version.
The text was updated successfully, but these errors were encountered: