chore: add release-please configuration, versioning tags

.github/workflows/release.yml

@@ -14,6 +14,20 @@ on:
     types: [published]
 
 jobs:
+  release-please:
+    name: Release Please
+    runs-on: ubuntu-24.04
+    outputs:
+      release_created: ${{ steps.release.outputs.release_created }}
+      tag_name: ${{ steps.release.outputs.tag_name }}
+    steps:
+      - name: Prepare release
+        id: release
+        uses: googleapis/release-please-action@45996ed1f6d02564a971a2fa1b5860e934307cf7
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          config-file: release-please-config.json
+          manifest-file: .release-please-manifest.json
   tag:
     name: Upload New Release
     runs-on: ubuntu-24.04

.release-please-manifest.json

@@ -0,0 +1,3 @@
+{
+	".": "1.1.3"
+}

oneupdate.php

@@ -10,7 +10,9 @@
  * License URI: https://www.gnu.org/licenses/gpl-2.0.txt
  * Text Domain: oneupdate
  * Domain Path: /languages
+ * x-release-please-start-version
  * Version: 1.1.3
+ * x-release-please-end
  * Requires PHP: 8.1
  * Requires at least: 6.8
  * Tested up to: 6.9
@@ -30,7 +32,7 @@ function constants(): void {
 	/**
 	 * Version of the plugin.
 	 */
-	define( 'ONEUPDATE_VERSION', '1.1.3' );
+	define( 'ONEUPDATE_VERSION', '1.1.3' ); // x-release-please-version.
 
 	/**
 	 * Root path to the plugin directory.

readme.txt

@@ -4,7 +4,9 @@ Donate link: https://rtcamp.com/
 Tags: plugin manager, CI/CD, automation, enterprise
 Requires at least: 6.8
 Tested up to: 6.9
+<!-- x-release-please-start-version -->
 Stable tag: 1.1.3
+<!-- x-release-please-end -->
 Requires PHP: 8.1
 License: GPLv2 or later
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
@@ -24,7 +26,7 @@ OneUpdate solves this by providing a centralized governing to manage all sites w
 **Key Benefits:**
 
 * **50% Time Savings:** Reduce plugin update process time significantly
-* **Cost Reduction:** Lower operational costs through workflow optimization  
+* **Cost Reduction:** Lower operational costs through workflow optimization
 * **Streamlined Workflow:** Centralized management while maintaining site autonomy
 * **Security:** REST API with unique authentication keys and secure S3 integration
 
@@ -62,7 +64,7 @@ OneUpdate solves this by providing a centralized governing to manage all sites w
 1. Upload the OneUpdate plugin files to the `/wp-content/plugins/oneupdate` directory, or install the plugin through the WordPress plugins screen directly
 2. Activate the plugin through the 'Plugins' screen in WordPress
 3. Set up one site as the "Governing Site" for centralized management
-4. Configure other sites as "Brand Sites" 
+4. Configure other sites as "Brand Sites"
 5. Add required GitHub Actions workflows to your repositories:
    * `oneupdate-pr-creation.yml` (for public plugins)
    * `oneupdate-pr-creation-private.yml` (for private plugins)

release-please-config.json

@@ -0,0 +1,21 @@
+{
+	"$schema": "https://raw.githubusercontent.com/googleapis/release-please/main/schemas/config.json",
+	"packages": {
+		".": {
+			"release-type": "php",
+			"changelog-path": "CHANGELOG.md",
+			"include-v-in-tag": true,
+			"bump-minor-pre-major": true,
+			"extra-files": [
+				{
+					"type": "generic",
+					"path": "oneupdate.php"
+				},
+				{
+					"type": "generic",
+					"path": "readme.txt"
+				}
+			]
+		}
+	}
+}