public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Than Ngo <than@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/chromium] epel9-next: - update to 130.0.6723.69
Date: Fri, 07 Aug 2026 16:07:05 GMT	[thread overview]
Message-ID: <178611882513.1.3911437275717764707.rpms-chromium-f73c0983b420@fedoraproject.org> (raw)

          A new commit has been pushed.

          Repo   : rpms/chromium
          Branch : epel9-next
          Commit : f73c0983b42004dc790b1b1b4a40b1c8d67dd347
          Author : Than Ngo <than@redhat.com>
          Date   : 2024-10-26T13:14:22+02:00
          Stats  : +9/-3 in 2 file(s)
          URL    : https://src.fedoraproject.org/rpms/chromium/c/f73c0983b42004dc790b1b1b4a40b1c8d67dd347?branch=epel9-next

          Log:
          - update to 130.0.6723.69
* High CVE-2024-10229: Inappropriate implementation in Extensions
* High CVE-2024-10230: Type Confusion in V8
* High CVE-2024-10231: Type Confusion in V8# Bitte geben Sie eine Commit-Beschreibung für Ihre Änderungen ein. Zeilen,

---
diff --git a/chromium.spec b/chromium.spec
index a1c75c4..94e49f5 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -273,8 +273,8 @@
 %endif
 
 Name:	chromium%{chromium_channel}
-Version: 130.0.6723.58
-Release: 2%{?dist}
+Version: 130.0.6723.69
+Release: 1%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
 License: BSD-3-Clause AND LGPL-2.1-or-later AND Apache-2.0 AND IJG AND MIT AND GPL-2.0-or-later AND ISC AND OpenSSL AND (MPL-1.1 OR GPL-2.0-only OR LGPL-2.0-only)
@@ -1917,6 +1917,12 @@ getent group chrome-remote-desktop >/dev/null || groupadd -r chrome-remote-deskt
 %endif
 
 %changelog
+* Sat Oct 26 2024 Than Ngo <than@redhat.com> - 130.0.6723.69-1
+- update to 130.0.6723.69
+  * High CVE-2024-10229: Inappropriate implementation in Extensions
+  * High CVE-2024-10230: Type Confusion in V8
+  * High CVE-2024-10231: Type Confusion in V8
+
 * Mon Oct 21 2024 Than Ngo <than@redhat.com> - 130.0.6723.58-2
 - Add missing pthread stack size for ppc64 (openpower-patches)
 

diff --git a/sources b/sources
index 2d850c6..3801e9b 100644
--- a/sources
+++ b/sources
@@ -2,4 +2,4 @@ SHA512 (node-v20.6.1-linux-arm64.tar.xz) = adfcaf2c22614797fd69fb46d94c1cbf64dea
 SHA512 (node-v20.6.1-linux-x64.tar.xz) = 7e15c05041a9a50f0046266aadb2e092a5aefbec19be1c7c809471add520cb57c7df3c47d88b1888b29bf2979dca3c92adddfd965370fa2a9da4ea02186464fd
 SHA512 (linux-arm64-0.19.2.tgz) = 8a0d8fec6786fffcd6954d00820037a55d61e60762c74300df0801f8db27057562c221a063bedfb8df56af9ba80abb366336987e881782c5996e6f871abd3dc6
 SHA512 (linux-x64-0.19.2.tgz) = a31cc74c4bfa54f9b75d735a1cfc944d3b5efb7c06bfba9542da9a642ae0b2d235ea00ae84d3ad0572c406405110fe7b61377af0fd15803806ef78d20fc6f05d
-SHA512 (chromium-130.0.6723.58-clean.tar.xz) = 1db9db62de458d0d6e45eb5017c5051fa35c06328e429b7f3331b4cc73c79ba5cbe6b394d3c0235f7860b3bede5c7ebaee1237a4db3fb934474614a32489de92
+SHA512 (chromium-130.0.6723.69-clean.tar.xz) = 68fd9e740e95d1cdd77ca2a6ef58500b7263be6f6a44170adff585a2de788abdff4dac0fc85b8c8bcf78b612062529ff65c0ae1c375acce30e4ec8b2aa4c6d48

                 reply	other threads:[~2026-08-07 16:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=178611882513.1.3911437275717764707.rpms-chromium-f73c0983b420@fedoraproject.org \
    --to=than@redhat.com \
    --cc=git-commits@fedoraproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox