Update to support WP 6.3

Author: jabranr

UPDATING.md

@@ -0,0 +1,17 @@
+# Update guide
+
+- change WordPress version in Dockerfile (Major version only)
+- run `docker-compose up`
+  -- installs and sets up the WordPress, database and plugins
+  -- creates a dev login for WP dashboard
+- enable API by changing permalink
+- add a custom ACF field
+- confirm the outcome from JSON endpoint http://localhost:8080/wp-json/acf/v3/posts
+- update version and change log in `readme.txt` and `index.php`
+- merge to master
+- install SVN (brew install svn) (if required)
+- run sh ./release.sh {new version}
+  -- creates version in SVN
+  -- pushes new tags into WordPress SVN
+  -- creates new git tag
+  -- pushes the change to GitHub

release.sh

@@ -29,3 +29,7 @@ svn cp svn/trunk "svn/tags/$1"
 echo "- Release to SVN remote";
 cd svn/
 svn ci -m "Release version $1" --username jabranr
+
+echo "- Tag the release and push";
+git tag $1 -m "Release v$1"
+git push --tags

src/index.php

@@ -5,7 +5,7 @@
  * Plugin URI: https://github.com/jabranr/nullify-empty-fields-for-acf
  * Description: Set Advanced Custom Fields (ACF) empty field value as <code>null</code> instead of <code>false</code> to avoid GraphQL error in GatsbyJS.
  * Author: Jabran Rafique <hello@jabran.me>
- * Version: 1.2.3
+ * Version: 1.2.4
  * Author URI: https://jabran.me?utm_source=nullify-empty-fields-for-acf
  * License: MIT License
  *

src/readme.txt

@@ -3,8 +3,8 @@ Contributors: jabranr
 Donate link: https://paypal.me/jabranr
 Tags: gatsby, graphql, acf, advanced-custom-fields, wordpress
 Requires at least: 5.0
-Tested up to: 6
-Stable tag: 1.2.3
+Tested up to: 6.3
+Stable tag: 1.2.4
 Requires PHP: 7.1
 License: MIT License
 License URI: https://opensource.org/licenses/MIT
@@ -27,6 +27,9 @@ Set Advanced Custom Fields (ACF) empty field value as `null` instead of `false`
 
 == Changelog ==
 
+= 1.2.4 =
+* Support for WordPress 6.3 as previous attempt to support major version only did not work
+
 = 1.2.3 =
 * Support for WordPress 6.x