Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:130221 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by lists.php.net (Postfix) with ESMTPS id 67A941A00BC for ; Mon, 2 Mar 2026 13:14:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1772457248; bh=kdJdVGxWUZ98T8w5Rmu+PRlZABTKPVvpKXOzaw+0D98=; h=Date:To:From:Subject:From; b=ZP4glrm28VzSjyedpciYUrgu+tzRkpZCzLrzPE4TO3Jq8TA1pZsA0GAtsuhpxQDQY 0a3qYYujxVNhnFPcBl9xxWLh1MGCVYyvWGKsrMtrYG3dKYlUPr1whFoCNTHBVGBBuA A6HI7Kn3ykYVCRvXcJoNj2PcVC4lo45rpleFYkVV1dfIXKjJ0k6+5BUWTlA39eoFYs 0k0t5IlctbN8SCKOCdHIyd1+dtpeln2se8v6Y6jQYty+gCRKzl5jq7bciNYMGbsVlS Cb3i1JK5Qt29NsvEMIeKxGnMH1zqLbs9U4mEUzBPMOfdmwLWz+Qnu4NA03w9kK3wYs yjd7pOAnqKC2Q== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 2A73C180078 for ; Mon, 2 Mar 2026 13:14:06 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,SPF_PASS autolearn=no autolearn_force=no version=4.0.1 X-Spam-Virus: No X-Envelope-From: Received: from mail-244118.protonmail.ch (mail-244118.protonmail.ch [109.224.244.118]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 2 Mar 2026 13:14:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gpb.moe; s=protonmail2; t=1772457238; x=1772716438; bh=kdJdVGxWUZ98T8w5Rmu+PRlZABTKPVvpKXOzaw+0D98=; h=Date:To:From:Subject:Message-ID:Feedback-ID:From:To:Cc:Date: Subject:Reply-To:Feedback-ID:Message-ID:BIMI-Selector; b=ZkWW3wcx99YaVvghek00Xh8WfgzvVX/XWSep4nh5XR2W/DAw3pTwubyZ1lbtPsSN3 fkFrlhnnN5wU/kVpcBdBqChSyyz4JE6+kXC+1SawUdq959U1LCoYAFMCzHqHdTb73Z g6fwYNheKBPuv1rXAtWkmpeEXrMYTTDD5OAMbDxoI9OPvdwVvrUrPtLcaoe7qBEPv5 oT6iTgBZzAQqYZKjWv/3E741+FW7CoM/cFHIt53CYH9hErE9WlWFEZPC5paRYhkJ8r DgEOtCw/mfKUmzCAyyfvbL9dwaOts9G8L2WGMsqsjGk6b/jxGiXutp5Glu6q+eiR37 4Lb6G5Fi7rZ5w== Date: Mon, 02 Mar 2026 13:13:52 +0000 To: PHP internals Subject: [PHP-DEV] [RFC] Exempt input type and value validation from BC Break policy Message-ID: Feedback-ID: 96993444:user:proton X-Pm-Message-ID: c75ac499f98e23c8153915423c1d290d1c59eb94 Precedence: list list-help: list-unsubscribe: list-post: List-Id: x-ms-reactions: disallow MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: internals@gpb.moe ("Gina P. Banyard") Hello internals, I would like to propose a short policy RFC to formally exempt input type an= d value validation from our BC Break policy. The current wording of the policy already permits us to add validation of i= nputs, but recently any such changes have been asked to submit an RFC inste= ad. We believe that requiring an RFC for this type of change is detrimental and= adds unnecessary friction for routine maintenance activity and new contrib= utors. RFC: https://wiki.php.net/rfc/policy-exempt-type-value-error-bc-policy Best regards, Gina P. Banyard