Skip to content

Generation 7019334052

Pre-release
Pre-release
Compare
Choose a tag to compare
@github-actions github-actions released this 28 Nov 13:20
7019334052
64f705f
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.

Version 120.0.6099.25
including the following changes since: 2023-11-26T00:42:16Z

Date: Tue Nov 28 13:11:01 2023 +0000
Limit message to 50 lines

Date: Tue Nov 28 10:17:53 2023 +0000
Implement new memory defragmentation strategy

Date: Tue Nov 28 06:34:14 2023 +0000
Disable SubsampledHistograms in Mojo

Date: Thu Oct 19 01:25:11 2023 +0000
[Extensions] Adjust the minimum alarm time to 30s for MV3 extensions

    Packed extensions have a limit of 60s for scheduling alarms. Relax this
    to 30s for MV3 extensions, since this matches the service worker idle
    timeout. Otherwise, it's not possible for an extension to effectively
    schedule an alarm for, say, 45 seconds from a given point.
    
    Bug: 1479570
    Change-Id: I158b5ebcd2160c7a2dc55e3ca0cd924339159fc5
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4950751
    Reviewed-by: David Bertoni <dbertoni@chromium.org>
    Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#1211894}
    (cherry picked from commit cbe4a1001db41accd848587884b1105dc545417e)

Date: Tue Oct 17 23:34:04 2023 +0000
[Extensions] Clean up Alarms API usage of TimeDelta

    The alarms API has limits on the minimum granularity for alarms.
    Currently, these use a weird (and conceptually incorrect, though the
    end result is the proper behavior) mishmash of TimeDelta and double
    multiplication to compare the limits.
    
    Fix this and just use base::TimeDelta, reducing LOC and improving
    readability.
    
    This CL has no behavior change.
    
    Bug: None
    Change-Id: I6d28b9278ff501aafc7f8839d3b6f26b55f3ba1f
    Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4949473
    Reviewed-by: Tim <tjudkins@chromium.org>
    Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
    Cr-Commit-Position: refs/heads/main@{#1211188}
    (cherry picked from commit d8526f42485f7f6c6bfd12e6340c94dd5883d1c6)

Date: Thu Aug 10 19:25:30 2023 +0000
Extensions: ExtensionId: Use alias instead of std::string

    Context:

This version will replace your currently installed Kiwi Browser (com.kiwibrowser.browser).
If you have important data, make sure to backup them or save them before upgrading to this version.

This release was automatically generated from GitHub refs/heads/kiwi in run ID 7019334052.

Summary:

  • To install / update Kiwi Browser, use "com.kiwibrowser.browser-arm64-7019334052-github.apk".
    If it doesn't work, try again using "com.kiwibrowser.browser-arm64-7019334052-playstore.apk" (if it exists).

Detailed information about the different files:

  • ".map" files are files that developers can use to investigate crashes (ProGuard mapping files), these files are not needed to run the browser and are for developers only.
  • ".apk" files are packages that you have to install to use Kiwi Browser.

The filenames are in the form "[PACKAGE_NAME]-[ARCHITECTURE]-[BUILD_VERSION]-[SIGNATURE_TYPE].apk"

If you want to keep the Play Store version installed, and still try the GitHub edition then you can install the APKs starting with "com.kiwibrowser.browser.dev" (you will keep all your Play Store bookmarks, settings and passwords, and the GitHub edition will be installed separately).

Build version:

  • Everytime a change is introduced in Kiwi Browser, a new build version is generated.

Architecture:

  • "-arm64" is compatible with modern devices and offers the best performance.
  • "-arm" is compatible with almost all devices and uses less memory.
  • "-x86" and "-x64" builds are compatible with emulators and Intel compatible tablets.

Signature type:

  • On Android, applications have to be signed by a developer before they can be installed.

Kiwi has two types of builds:

Signed by the developer:

  • "-github.apk" are builds signed using the official developer key.
    A signed build is a build that comes straight from the GitHub official repository and is always the most updated.

Play Certified by Google:

  • Once in a while, we send a "-github.apk" build to be reviewed and signed by Google.
    Google reviews the application, checks that the application is not malicious, adds the "Google Play Certified" badge, signs the file and this becomes "-playstore.apk".

We then distribute "-playstore.apk" on Google Play, XDA-Developers, Samsung and other app stores.

This process takes some time and is partially manual so not all GitHub builds have a "-playstore.apk".

On Android, you can install an update to an application only if it was signed by the same developer as the version that you currently have installed:

  • You can install a "-github.apk" build on top of a "-github.apk" build, and a "-playstore.apk" build on top of a "-playstore.apk" build.
  • You cannot install a "-playstore.apk" build on top of a "-github.apk" build.

Essentially, if you downloaded Kiwi from an app store, you need to use the "-playstore.apk" files or uninstall the version of Kiwi you have and start using the "-github.apk" version.

Assets 10
Loading