public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Paul Howarth <paul@city-fan.org>
To: git-commits@fedoraproject.org
Subject: [rpms/perl-Cpanel-JSON-XS] rawhide: Update to 4.42
Date: Sun, 07 Jun 2026 10:43:31 GMT	[thread overview]
Message-ID: <178082901147.1.8966247915781618159.rpms-perl-Cpanel-JSON-XS-4c419b0508c4@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/perl-Cpanel-JSON-XS
            Branch : rawhide
            Commit : 4c419b0508c44c83f08b8e5c008f03cf16f0c5b5
            Author : Paul Howarth <paul@city-fan.org>
            Date   : 2026-06-07T11:42:46+01:00
            Stats  : +34/-2 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/perl-Cpanel-JSON-XS/c/4c419b0508c44c83f08b8e5c008f03cf16f0c5b5?branch=rawhide

            Log:
            Update to 4.42

- New upstream release 4.42
  - Ensure encode with a type spec hashref does not change the hashref argument
    (GH#240)
  - Fix -e docs: "written" → "read" (GH#239)
  - Fix Boolean eq overload matching undef (GH#207); Cpanel::JSON::XS::Boolean
    overloaded eq would match undef as equal to false because undef stringifies
    to "" - added defined() guard
  - Fix error messages showing overloaded stringification for blessed objects
    (GH#191); error messages now use ClassName=TYPE(addr) format, bypassing any
    "" overload
  - Fix type_all_string overriding allow_blessed/convert_blessed (GH#175); with
    type_all_string + allow_blessed, blessed objects are now encoded as null
    (not stringified as HASH address)
  - Fix infinite recursion when encode is called from a "" overload (GH#128);
    the recursion guard temporarily clears convert_blessed and allow_stringify
    flags on the JSON object before calling the overload, preventing re-entrant
    encode loops
  - Fix $obj->new creating a broken object (GH#93); when new() is called on an
    existing object (e.g. $json->new->new), the class name is now extracted
    from the object's stash rather than using the stringified reference
  - Change allow_nonref default to true (GH#241, matching JSON::PP and
    JSON::XS 4.0+ and the insecure RFC 7159); encode and decode now accept
    non-reference values by default; decode_json() with an explicit 0/1 second
    argument still works; allow_nonref(0) to disable scalars-only for secure
    JSON
  - Fix minor t/12_blessed.t typo
  - Fix GH#112: encode large whole-number NV values without .0 on 32-bit Perl
    (values exceeding UV_MAX that Perl stores as float)
  - Fix GH#197: prefer IOK over pNOK when encoding values where IV is accurate
    but NV is imprecise (SvNOK not set)

---
diff --git a/perl-Cpanel-JSON-XS.spec b/perl-Cpanel-JSON-XS.spec
index 2c0938d..806ee79 100644
--- a/perl-Cpanel-JSON-XS.spec
+++ b/perl-Cpanel-JSON-XS.spec
@@ -7,7 +7,7 @@
 
 Name:		perl-Cpanel-JSON-XS
 Summary:	JSON::XS for Cpanel, fast and correct serializing
-Version:	4.41
+Version:	4.42
 Release:	1%{?dist}
 License:	GPL-1.0-or-later OR Artistic-1.0-Perl
 URL:		https://metacpan.org/release/Cpanel-JSON-XS
@@ -164,6 +164,38 @@ make test
 %{_mandir}/man3/Cpanel::JSON::XS::Type.3*
 
 %changelog
+* Sun Jun  7 2026 Paul Howarth <paul@city-fan.org> - 4.42-1
+- Update to 4.42
+  - Ensure encode with a type spec hashref does not change the hashref argument
+    (GH#240)
+  - Fix -e docs: "written" → "read" (GH#239)
+  - Fix Boolean eq overload matching undef (GH#207); Cpanel::JSON::XS::Boolean
+    overloaded eq would match undef as equal to false because undef stringifies
+    to "" - added defined() guard
+  - Fix error messages showing overloaded stringification for blessed objects
+    (GH#191); error messages now use ClassName=TYPE(addr) format, bypassing any
+    "" overload
+  - Fix type_all_string overriding allow_blessed/convert_blessed (GH#175); with
+    type_all_string + allow_blessed, blessed objects are now encoded as null
+    (not stringified as HASH address)
+  - Fix infinite recursion when encode is called from a "" overload (GH#128);
+    the recursion guard temporarily clears convert_blessed and allow_stringify
+    flags on the JSON object before calling the overload, preventing re-entrant
+    encode loops
+  - Fix $obj->new creating a broken object (GH#93); when new() is called on an
+    existing object (e.g. $json->new->new), the class name is now extracted
+    from the object's stash rather than using the stringified reference
+  - Change allow_nonref default to true (GH#241, matching JSON::PP and
+    JSON::XS 4.0+ and the insecure RFC 7159); encode and decode now accept
+    non-reference values by default; decode_json() with an explicit 0/1 second
+    argument still works; allow_nonref(0) to disable scalars-only for secure
+    JSON
+  - Fix minor t/12_blessed.t typo
+  - Fix GH#112: encode large whole-number NV values without .0 on 32-bit Perl
+    (values exceeding UV_MAX that Perl stores as float)
+  - Fix GH#197: prefer IOK over pNOK when encoding values where IV is accurate
+    but NV is imprecise (SvNOK not set)
+
 * Thu May 28 2026 Paul Howarth <paul@city-fan.org> - 4.41-1
 - Update to 4.41
   - Fix BOM-shift PV-corruption SIGABRT (CVE-2026-9516)

diff --git a/sources b/sources
index bfb4540..2552306 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Cpanel-JSON-XS-4.41.tar.gz) = 5479b0129d5e2210baf094cefe1eabf810aca81335ee7eb7f6da4644b5598ead97989baade946f0ec80da63b577a04c5fde6637a2669d800386be6b400c55777
+SHA512 (Cpanel-JSON-XS-4.42.tar.gz) = a9898810660bff56234b3c9296c88a2d3422793f053ffa76689d9141105d017d29efb479812cb255bc981f178fc6bba7e21ffbf7e3783975100fa33e38084b2d

                 reply	other threads:[~2026-06-07 10:43 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=178082901147.1.8966247915781618159.rpms-perl-Cpanel-JSON-XS-4c419b0508c4@fedoraproject.org \
    --to=paul@city-fan.org \
    --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