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 147.0.7727.116
Date: Fri, 07 Aug 2026 16:08:54 GMT	[thread overview]
Message-ID: <178611893468.1.7048472221085819458.rpms-chromium-48b92268e9a8@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/chromium
Branch : epel9-next
Commit : 48b92268e9a835fe626c770d72892b8eb204a460
Author : Than Ngo <than@redhat.com>
Date   : 2026-04-23T09:29:47+02:00
Stats  : +5/-2 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/chromium/c/48b92268e9a835fe626c770d72892b8eb204a460?branch=epel9-next

Log:
Update to 147.0.7727.116

---
diff --git a/chromium.spec b/chromium.spec
index 74fe266..63b74fe 100644
--- a/chromium.spec
+++ b/chromium.spec
@@ -262,7 +262,7 @@
 %endif
 
 Name:	chromium
-Version: 147.0.7727.101
+Version: 147.0.7727.116
 Release: 1%{?dist}
 Summary: A WebKit (Blink) powered web browser that Google doesn't want you to use
 Url: http://www.chromium.org/Home
@@ -1857,6 +1857,9 @@ fi
 %endif
 
 %changelog
+* Thu Apr 23 2026 Than Ngo <than@redhat.com> - 147.0.7727.116-1
+- Update to 147.0.7727.116
+
 * Wed Apr 15 2026 Than Ngo <than@redhat.com> - 147.0.7727.101-1
 - Update to 147.0.7727.101
   * Critical CVE-2026-6296: Heap buffer overflow in ANGLE

diff --git a/sources b/sources
index bf44dd0..b1334fe 100644
--- a/sources
+++ b/sources
@@ -1,4 +1,4 @@
 SHA512 (rollup-linux-arm64-gnu-4.22.4.tgz) = 01d3d1a0d8b734a54ba2508dfd2a7817837577df1ce120671cc2a82ee886e915e0a19e2c965b1eb868a8b33ba69cf1a63ccd8eeea6805ff20975e0d4f1fdba03
 SHA512 (rollup-linux-powerpc64le-gnu-4.22.4.tgz) = dda5422bdc5f596d68190a53b182493c5e9b7e959f85b46785d97285a936662c852c369acb3d043f98fd5754552c003196658a4c37d2f70c91c98de1be13e83a
 SHA512 (node-v22.22.0-stripped.tar.gz) = f32a8a73063b3c78cbacf941e11dd529ebcf2618b3ba661966312e49ee9870c43a3acf256e8d331a4b0b621b16a501810c02a3ad763c75884cc250addca8e106
-SHA512 (chromium-147.0.7727.101-clean.tar.xz) = 86044f16b5124dcb90d939666dbeed422fc285e7df2f8807aed75b64a39c37f6a0f0db00e014b5bfba12dd40b14a8c9d148f26ccbad1f16f3c1d5c7c7eaa713c
+SHA512 (chromium-147.0.7727.116-clean.tar.xz) = aed20a35d1877ca66846f1fa73f6f95ecb24c5c2dfed7a28c56cfb6edc55619637ffa0c047322b4ef50eea43adc5d902a68508c9b6faf51e64d4225b2785bebc

                 reply	other threads:[~2026-08-07 16:08 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=178611893468.1.7048472221085819458.rpms-chromium-48b92268e9a8@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