Update PHP to 8.1

composer.json

@@ -30,7 +30,7 @@
 			"composer/installers": true
 		},
     "platform": {
-      "php": "7.4"
+      "php": "8.1"
     }
 	}
 }

phpcs.override.xml

@@ -1,6 +1,6 @@
 <?xml version="1.0"?>
 <ruleset name="WordPress LH Override">
 	<description>The only purpose of this ruleset is to override the testVersion of other rulesets.</description>
-	<!-- Check for cross-version support for PHP 7.4 and higher. -->
-	<config name="testVersion" value="7.4-"/>
+	<!-- Check for cross-version support for PHP 8.1 and higher. -->
+	<config name="testVersion" value="8.1-"/>
 </ruleset>

phpcs.xml

@@ -11,14 +11,18 @@
 		the equality operator is very close to the assignment operator.
 		It's easy to mess up and accidentally assign to the variable you're
 		trying to check.
+
 		Here's the thing though. Yoda conditions just don't read correctly
 		in the code flow. They require you to change the way you think
 		about the control flow.
+
 		Rather than forcing every conditional to be backwards, why not ban
 		assignment from conditionals? You never really *need* to assign in
 		a conditional.
+
 		So, here's where I stand: no to Yoda conditions. Yes to banning
 		assignment in conditionals.
+
 		Thank you Human Made!
 		-->
 		<exclude name="WordPress.PHP.YodaConditions" />
@@ -56,5 +60,11 @@
 		</properties>
 	</rule>
 
+	<!--
+	Prevent errors caused by WordPress Coding Standards not supporting PHP 8.0+.
+	See https://github.com/WordPress/WordPress-Coding-Standards/issues/2035
+	-->
+	<ini name="error_reporting" value="E_ALL &#38; ~E_DEPRECATED" />
+
 	<rule ref="phpcs.override.xml"/>
 </ruleset>

plugin/composer.json

@@ -11,5 +11,10 @@
     "psr-4": {
       "WpMunich\\lhpbpp\\": "inc/"
     }
+  },
+  "config": {
+    "platform": {
+      "php": "8.1"
+    }
   }
 }

theme/composer.json

@@ -10,6 +10,9 @@
   "config": {
     "allow-plugins": {
       "bamarni/composer-bin-plugin": true
+    },
+    "platform": {
+      "php": "8.1"
     }
   }
 }