similarity index 94%
rename from meta/recipes-connectivity/libuv/libuv_1.48.0.bb
rename to meta/recipes-connectivity/libuv/libuv_1.49.0.bb
@@ -6,7 +6,7 @@ LICENSE = "MIT"
LIC_FILES_CHKSUM = "file://LICENSE;md5=74b6f2f7818a4e3a80d03556f71b129b \
file://LICENSE-extra;md5=f9307417749e19bd1d6d68a394b49324"
-SRCREV = "e9f29cb984231524e3931aa0ae2c5dae1a32884e"
+SRCREV = "d2e56a5e8d3e39947b78405ca6e4727c70f5568a"
SRC_URI = "git://github.com/libuv/libuv.git;branch=v1.x;protocol=https"
UPSTREAM_CHECK_GITTAGREGEX = "v(?P<pver>\d+(\.\d+)+)"
Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe(s) *libuv* to *1.49.0* has Succeeded. Next steps: - apply the patch: git am 0001-libuv-upgrade-1.48.0-1.49.0.patch - check the changes to upstream patches and summarize them in the commit message, - compile an image that contains the package - perform some basic sanity tests - amend the patch and sign it off: git commit -s --reset-author --amend - send it to the appropriate mailing list Alternatively, if you believe the recipe should not be upgraded at this time, you can fill RECIPE_NO_UPDATE_REASON in respective recipe file so that automatic upgrades would no longer be attempted. Please review the attached files for further information and build/update failures. Any problem please file a bug at https://bugzilla.yoctoproject.org/enter_bug.cgi?product=Automated%20Update%20Handler Regards, The Upgrade Helper -- >8 -- From 1cb6365acd0a759e97899eafca2307247572e47e Mon Sep 17 00:00:00 2001 From: Upgrade Helper <auh@yoctoproject.org> Date: Thu, 10 Oct 2024 12:16:59 +0000 Subject: [PATCH] libuv: upgrade 1.48.0 -> 1.49.0 --- .../libuv/{libuv_1.48.0.bb => libuv_1.49.0.bb} | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) rename meta/recipes-connectivity/libuv/{libuv_1.48.0.bb => libuv_1.49.0.bb} (94%)