From: Adrian Perez de Castro <aperez@igalia.com>
To: buildroot@buildroot.org
Cc: Adrian Perez de Castro <aperez@igalia.com>
Subject: [Buildroot] [PATCH] package/cage: bump to version 0.3.1
Date: Fri, 11 Sep 2026 01:02:05 +0200 [thread overview]
Message-ID: <20260910230207.1934197-1-aperez@igalia.com> (raw)
This minor release fixes a crash that could happen when a surface
requests to be fullscreened right away during startup. Release notes:
https://github.com/cage-kiosk/cage/releases/tag/v0.3.1
Signed-off-by: Adrian Perez de Castro <aperez@igalia.com>
---
package/cage/cage.hash | 2 +-
package/cage/cage.mk | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/cage/cage.hash b/package/cage/cage.hash
index 4b05602822..34585cda28 100644
--- a/package/cage/cage.hash
+++ b/package/cage/cage.hash
@@ -1,5 +1,5 @@
# Locally computed, after checking PGP signature
-sha256 cd2510f83bef3e08e660d99492ca7761b218ecb53ee01cdbbeee3d6aabc7734e cage-0.3.0.tar.gz
+sha256 edafc173b6f56a3e1564933e272a54aaa9fe158d330e6a415d57b44ab880fe2b cage-0.3.1.tar.gz
# Hashes for license files:
sha256 e117104073335dbaf78596fb1bedf89dda63c71f60f0b665947b2d369c77ecee LICENSE
diff --git a/package/cage/cage.mk b/package/cage/cage.mk
index 4495c59b4f..4372c4667c 100644
--- a/package/cage/cage.mk
+++ b/package/cage/cage.mk
@@ -4,7 +4,7 @@
#
################################################################################
-CAGE_VERSION = 0.3.0
+CAGE_VERSION = 0.3.1
CAGE_SITE = https://github.com/cage-kiosk/cage/releases/download/v$(CAGE_VERSION)
CAGE_LICENSE = MIT
CAGE_LICENSE_FILES = LICENSE
--
2.55.0
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2026-09-10 23:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 23:02 Adrian Perez de Castro [this message]
2026-09-13 9:53 ` [Buildroot] [PATCH] package/cage: bump to version 0.3.1 Julien Olivain via buildroot
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=20260910230207.1934197-1-aperez@igalia.com \
--to=aperez@igalia.com \
--cc=buildroot@buildroot.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