Merge branch 'main' of gitea.wpallstars.com:wpallstars/fix-plugin-does-not-exist-notices

git checkout main
Merge tag 'v1.6.4'

Release version 1.6.4

.ai-assistant.md

@@ -41,7 +41,10 @@ When updating the version number, always update these files:
 1. `fix-plugin-does-not-exist-notices.php` (Plugin header)
 2. `CHANGELOG.md` (Add new version section)
 3. `readme.txt` (Stable tag and Changelog section)
-4. Update `FPDEN_VERSION` constant in the main plugin file
+4. `README.md` (Update Changelog section to match readme.txt)
+5. Update `FPDEN_VERSION` constant in the main plugin file
+
+**IMPORTANT**: Always ensure README.md is kept in sync with readme.txt for consistency across platforms.
 
 ## Git Workflow
 
@@ -58,23 +61,48 @@ When updating the version number, always update these files:
 - Keep the first line under 50 characters
 - Reference issues when relevant: "Fix #123: Resolve plugin detection issue"
 
+### Pre-Release Checklist
+
+Before creating a new release, verify the following:
+
+- [ ] Determine the correct version increment (MAJOR, MINOR, or PATCH) based on the changes
+- [ ] Ensure all changes are documented in CHANGELOG.md
+- [ ] Verify all code changes are tested and working correctly
+- [ ] Check that all files are properly formatted and follow WordPress coding standards
+- [ ] Ensure Git Updater configuration is correct (if applicable)
+
 ### Release Process
 
 1. Create a new branch for the version: `git checkout -b v{MAJOR}.{MINOR}.{PATCH}`
-2. Update version numbers in all required files
+2. Update version numbers in ALL required files:
+   - `fix-plugin-does-not-exist-notices.php` (Plugin header)
+   - `FPDEN_VERSION` constant in the main plugin file
+   - `readme.txt` (Stable tag)
+   - `README.md` (Ensure changelog is updated)
+   - `languages/fix-plugin-does-not-exist-notices.pot` (Project-Id-Version)
+   - Any other files that reference the version number
 3. Update CHANGELOG.md with all changes
-4. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
-5. Push branch to all remotes:
+4. Update readme.txt changelog section
+5. Update README.md changelog section to match readme.txt
+6. Commit changes: `git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"`
+7. Test changes locally on the version branch
+8. When satisfied with testing, merge to main:
    ```
-   git push github HEAD:v{MAJOR}.{MINOR}.{PATCH}
-   git push gitea HEAD:v{MAJOR}.{MINOR}.{PATCH}
+   git checkout main
+   git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
    ```
-6. Create and push a tag to trigger the GitHub Actions workflow:
+9. Push main to all remotes:
+   ```
+   git push github main
+   git push gitea main
+   ```
+10. Create and push a tag to trigger the GitHub Actions workflow:
     ```
     git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
     git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
     git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
     ```
+11. Verify the GitHub Actions workflow completes successfully
 
 ## Build Process
 
@@ -120,23 +148,33 @@ Before releasing:
 
 ```
 # 1. Create a new branch
+git checkout main
 git checkout -b v1.7.0
 
-# 2. Update version numbers in files
+# 2. Update version numbers in ALL required files
 # - fix-plugin-does-not-exist-notices.php
 # - CHANGELOG.md
 # - readme.txt
+# - README.md
+# - languages/fix-plugin-does-not-exist-notices.pot
 # - FPDEN_VERSION constant
 
 # 3. Commit changes
 git add .
 git commit -m "Prepare release v1.7.0"
 
-# 4. Push to remotes
-git push github HEAD:v1.7.0
-git push gitea HEAD:v1.7.0
+# 4. Test changes locally on the version branch
+# (Run tests, verify functionality)
 
-# 5. Create and push tag
+# 5. Merge to main when ready
+git checkout main
+git merge v1.7.0 --no-ff
+
+# 6. Push main to remotes
+git push github main
+git push gitea main
+
+# 7. Create and push tag
 git tag -a v1.7.0 -m "Release version 1.7.0"
 git push github refs/tags/v1.7.0
 git push gitea refs/tags/v1.7.0
@@ -145,29 +183,53 @@ git push gitea refs/tags/v1.7.0
 ### Adding a New Feature
 
 ```
-# 1. Create feature branch
+# 1. Create feature branch from main
+git checkout main
 git checkout -b feature/new-feature-name
 
 # 2. Make changes and commit
 git add .
 git commit -m "Add new feature"
 
-# 3. Push to remotes
-git push github HEAD:feature/new-feature-name
-git push gitea HEAD:feature/new-feature-name
+# 3. Test locally
+# (Run tests, verify functionality)
+
+# 4. When ready for release, merge to a version branch
+git checkout -b v1.7.0
+git merge feature/new-feature-name --no-ff
+
+# 5. Continue with the release process
+# (Update version numbers, etc.)
 ```
 
 ### Fixing a Bug
 
 ```
-# 1. Create bugfix branch
+# 1. Create bugfix branch from main
+git checkout main
 git checkout -b fix/bug-description
 
 # 2. Make changes and commit
 git add .
 git commit -m "Fix #123: Fix bug description"
 
-# 3. Push to remotes
-git push github HEAD:fix/bug-description
-git push gitea HEAD:fix/bug-description
+# 3. Test locally
+# (Run tests, verify functionality)
+
+# 4. When ready for release, merge to a version branch
+git checkout -b v1.6.5
+git merge fix/bug-description --no-ff
+
+# 5. Continue with the release process
+# (Update version numbers, etc.)
+```
+
+### Testing a Previous Version
+
+```
+# Checkout a specific tag for testing
+git checkout v1.6.3
+
+# Or create a test branch from a specific tag
+git checkout v1.6.3 -b test/some-feature
 ```

.github/ai-workflows/bug-fixing.md

@@ -64,27 +64,60 @@ git commit -m "Fix #123: Brief description of the bug fix"
 
 If there's an issue number, reference it in the commit message.
 
-### 7. Push to Remote
+### 7. Prepare for Release
 
-Push the bug fix branch to the remote repositories:
+When the bug fix is ready to be released:
+
+1. Create a version branch for the release:
+
+```bash
+git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+```
+
+2. Merge your bug fix branch into the version branch:
+
+```bash
+git merge fix/bug-description --no-ff
+```
+
+3. Update version numbers and changelog entries
+
+4. Follow the standard release process from this point
+
+### 8. Push to Remote (Optional for Collaboration)
+
+If you need to collaborate with others on the bug fix before it's ready for release:
 
 ```bash
 git push github HEAD:fix/bug-description
 git push gitea HEAD:fix/bug-description
 ```
 
-### 8. Create Pull Request (Optional)
+### 9. Create Pull Request (Optional)
 
-If the repository uses pull requests for code review, create a pull request from the bug fix branch to the main branch.
+If the repository uses pull requests for code review, create a pull request from the bug fix branch to the version branch.
 
 ## Determining Version Increment
 
 After fixing a bug, determine the appropriate version increment:
 
 - **PATCH** (e.g., 1.6.0 → 1.6.1): For most bug fixes that don't change functionality
+  - **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
 - **MINOR** (e.g., 1.6.0 → 1.7.0): For bug fixes that introduce new features or significant changes
 - **MAJOR** (e.g., 1.6.0 → 2.0.0): For bug fixes that introduce breaking changes
 
+## Testing Previous Versions
+
+To test a previous version of the plugin:
+
+```bash
+# Checkout a specific tag for testing
+git checkout v{MAJOR}.{MINOR}.{PATCH}
+
+# Or create a test branch from a specific tag
+git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
+```
+
 ## Hotfix Process
 
 For critical bugs that need immediate fixing in a released version:
@@ -108,6 +141,8 @@ Increment the PATCH version and update all version numbers:
 - FPDEN_VERSION constant
 - CHANGELOG.md
 - readme.txt
+- README.md
+- languages/fix-plugin-does-not-exist-notices.pot (Project-Id-Version)
 
 ### 4. Commit and Push
 

.github/ai-workflows/feature-development.md

@@ -33,6 +33,7 @@ Update relevant documentation to reflect the new feature:
 - Add a description to CHANGELOG.md under an "Unreleased" section
 - Update readme.txt if the feature affects user-facing functionality
 - Update inline documentation/comments
+- Remember that any feature addition will require a version increment in all relevant files
 
 ### 4. Testing
 
@@ -52,18 +53,38 @@ git add .
 git commit -m "Add feature: descriptive name"
 ```
 
-### 6. Push to Remote
+### 6. Prepare for Release
 
-Push the feature branch to the remote repositories:
+When the feature is ready to be released:
+
+1. Create a version branch for the release:
+
+```bash
+git checkout -b v{MAJOR}.{MINOR}.{PATCH}
+```
+
+2. Merge your feature branch into the version branch:
+
+```bash
+git merge feature/descriptive-name --no-ff
+```
+
+3. Update version numbers and changelog entries
+
+4. Follow the standard release process from this point
+
+### 7. Push to Remote (Optional for Collaboration)
+
+If you need to collaborate with others on the feature before it's ready for release:
 
 ```bash
 git push github HEAD:feature/descriptive-name
 git push gitea HEAD:feature/descriptive-name
 ```
 
-### 7. Create Pull Request (Optional)
+### 8. Create Pull Request (Optional)
 
-If the repository uses pull requests for code review, create a pull request from the feature branch to the main branch.
+If the repository uses pull requests for code review, create a pull request from the feature branch to the version branch.
 
 ## Code Standards and Best Practices
 

.github/ai-workflows/release-process.md

@@ -15,6 +15,7 @@ This document provides step-by-step instructions for AI assistants to help with
 Based on the changes made, determine the appropriate version increment:
 
 1. **PATCH** (e.g., 1.6.0 → 1.6.1): For bug fixes and minor improvements
+   - **IMPORTANT**: Always increment the patch version for every change, even small ones, to make rollbacks easier if issues are found in testing
 2. **MINOR** (e.g., 1.6.0 → 1.7.0): For new features and significant improvements
 3. **MAJOR** (e.g., 1.6.0 → 2.0.0): For breaking changes
 
@@ -72,7 +73,16 @@ Add a new section at the top of the CHANGELOG.md file:
 - Bug fix 2
 ```
 
-#### c. readme.txt
+#### c. POT File (languages/fix-plugin-does-not-exist-notices.pot)
+
+Update the Project-Id-Version and POT-Creation-Date:
+
+```
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices {MAJOR}.{MINOR}.{PATCH}\n"
+"POT-Creation-Date: YYYY-MM-DDT00:00:00+00:00\n"
+```
+
+#### d. readme.txt
 
 Update the stable tag:
 
@@ -102,18 +112,38 @@ Brief description of the most important changes in this release
 ### 3. Commit Changes
 
 ```bash
-git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt
+git add fix-plugin-does-not-exist-notices.php CHANGELOG.md readme.txt README.md languages/fix-plugin-does-not-exist-notices.pot
 git commit -m "Prepare release v{MAJOR}.{MINOR}.{PATCH}"
 ```
 
-### 4. Push Branch to Remotes
+### 4. Test Changes Locally
+
+Test the changes thoroughly on the version branch to ensure everything works as expected:
+
+- Test with the latest WordPress version
+- Test with PHP 7.0+ (minimum supported version)
+- Verify all features work as expected
+- Check for any PHP warnings or notices
+
+### 5. Merge to Main
+
+When satisfied with testing, merge the version branch to main:
 
 ```bash
-git push github HEAD:v{MAJOR}.{MINOR}.{PATCH}
-git push gitea HEAD:v{MAJOR}.{MINOR}.{PATCH}
+git checkout main
+git merge v{MAJOR}.{MINOR}.{PATCH} --no-ff
 ```
 
-### 5. Create and Push Tag
+The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
+
+### 6. Push Main to Remotes
+
+```bash
+git push github main
+git push gitea main
+```
+
+### 7. Create and Push Tag
 
 ```bash
 git tag -a v{MAJOR}.{MINOR}.{PATCH} -m "Release version {MAJOR}.{MINOR}.{PATCH}"
@@ -121,17 +151,29 @@ git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH}
 git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH}
 ```
 
-### 6. Monitor GitHub Actions
+### 8. Monitor GitHub Actions
 
 Open the GitHub Actions page to monitor the build and deployment process:
 https://github.com/wpallstars/fix-plugin-does-not-exist-notices/actions
 
-### 7. Verify Release
+### 9. Verify Release
 
 - [ ] Check that the GitHub release was created successfully
 - [ ] Verify that the plugin was deployed to WordPress.org
 - [ ] Test the plugin from WordPress.org to ensure it works correctly
 
+## Testing Previous Versions
+
+To test a previous version of the plugin:
+
+```bash
+# Checkout a specific tag for testing
+git checkout v{MAJOR}.{MINOR}.{PATCH}
+
+# Or create a test branch from a specific tag
+git checkout v{MAJOR}.{MINOR}.{PATCH} -b test/some-feature
+```
+
 ## Rollback Procedure (If Needed)
 
 If issues are discovered after release:
@@ -151,16 +193,27 @@ Make the necessary changes to fix the issues.
 
 Increment the PATCH version and update all version numbers as described above.
 
-### 4. Commit and Push
+### 4. Test the Hotfix
+
+Test the hotfix thoroughly to ensure it resolves the issue without introducing new problems.
+
+### 5. Commit Changes
 
 ```bash
 git add .
 git commit -m "Fix issues in v{MAJOR}.{MINOR}.{PATCH}"
-git push github HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
-git push gitea HEAD:hotfix/v{MAJOR}.{MINOR}.{PATCH+1}
 ```
 
-### 5. Create and Push Tag
+### 6. Merge to Main
+
+```bash
+git checkout main
+git merge hotfix/v{MAJOR}.{MINOR}.{PATCH+1} --no-ff
+git push github main
+git push gitea main
+```
+
+### 7. Create and Push Tag
 
 ```bash
 git tag -a v{MAJOR}.{MINOR}.{PATCH+1} -m "Hotfix release version {MAJOR}.{MINOR}.{PATCH+1}"
@@ -168,6 +221,6 @@ git push github refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
 git push gitea refs/tags/v{MAJOR}.{MINOR}.{PATCH+1}
 ```
 
-### 6. Monitor and Verify
+### 8. Monitor and Verify
 
-Follow steps 6 and 7 from the release process to monitor and verify the hotfix release.
+Follow steps 8 and 9 from the release process to monitor and verify the hotfix release.

CHANGELOG.md

@@ -2,13 +2,30 @@
 
 All notable changes to this project will be documented in this file.
 
+## [1.6.4] - 2024-05-16
+### Improved
+- Version management to ensure consistent patch version increments
+- Documentation for version update process
+- AI workflow files with detailed version increment instructions
+
+## [1.6.3] - 2024-05-15
+### Fixed
+- Git Updater repository URLs to use full repository paths
+- Update URI configuration for proper update detection
+- Version management following semantic versioning
+
+### Changed
+- Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+- Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
 ## [1.6.2] - 2024-05-15
 ### Changed
 - Updated POT file version for consistency
 - Improved JavaScript localization with proper fallbacks
 - Enhanced code quality for WordPress.org submission
-- Fixed Git Updater configuration with correct Update URI
-- Improved update server URL configuration
+### Added
+- Git Updater configuration with Update URI
+- Update server URL configuration
 
 ## [1.6.1] - 2024-05-15
 ### Added

README.md

@@ -120,35 +120,46 @@ The plugin works by:
 
 ## Changelog
 
-### 1.4.1
-- Added FAQ about keeping the plugin installed after notices are cleared
+### 1.6.4
+* Updated version management to ensure consistent patch version increments
+* Improved documentation for version update process
+* Enhanced AI workflow files with detailed version increment instructions
 
-### 1.4.0
-- Updated plugin name and text domain
-- Repository rename from plugin-reference-cleaner to fix-plugin-does-not-exist-notices
+### 1.6.3
+* Fixed Git Updater repository URLs to use full repository paths
+* Corrected Update URI configuration for proper update detection
+* Improved version management following semantic versioning
+* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
 
-### 1.3.3
-* Improved notification placement next to WordPress error messages
-* Added "Click here to scroll" button that automatically locates missing plugins
-* Enhanced reliability with multiple injection methods
-* Added visual arrow pointing from notification to error message
+### 1.6.2
+* Updated POT file version for consistency
+* Improved JavaScript localization with proper fallbacks
+* Enhanced code quality for WordPress.org submission
+* Added Git Updater configuration with Update URI
+* Added update server URL configuration
 
-### 1.3.2
-* Added prominent notification directly below WordPress error messages
-* Improved user guidance with visual cues to connect error and solution
-* Added eye-catching styling to help users understand how to fix errors
+### 1.6.1
+* Added AI assistant guide and workflow documentation
+* Added detailed release process documentation
+* Added feature development guidelines
+* Added bug fixing procedures
+* Added code review standards
 
-### 1.3.1
-* Added instructional notification explaining how to use the plugin
-* Improved user guidance with step-by-step instructions
-* Enhanced visual identification of missing plugins
+### 1.6.0
+* Added full translation support with POT file
+* Added JavaScript localization for better multilingual support
+* Added plugin constants for improved code organization
+* Added Git Updater support for updates from GitHub and Gitea
+* Updated code to follow WordPress internationalization best practices
+* Improved asset loading with version constants
+* Added smart update detection based on installation source
 
-### 1.3.0
-* Complete redesign for maximum compatibility with all WordPress themes
-* Now adds missing plugins directly to the plugins list table
-* Uses standard WordPress admin UI patterns instead of DOM manipulation
-* Added "Remove Reference" action link in the plugins list
-* Significantly improved reliability across all WordPress configurations
+### 1.5.0
+* Improved compatibility with WordPress 6.4
+* Enhanced error detection for plugin references
+* Minor UI improvements for better visibility
+* Accessibility enhancements for screen readers
 
 [View full changelog](CHANGELOG.md)
 
@@ -158,4 +169,4 @@ This project is licensed under the GPL-2.0+ License - see the [LICENSE](LICENSE)
 
 ## Support
 
-For support, please visit [WP All Stars](https://www.wpallstars.com). 
+For support, please visit [WP ALLSTARS](https://www.wpallstars.com).

fix-plugin-does-not-exist-notices.php

@@ -4,14 +4,16 @@
  *
  * @package           FixPluginDoesNotExistNotices
  * @author            Marcus Quinn
- * @copyright         2023 WP All Stars
+ * @copyright         2023 WP ALLSTARS
  * @license           GPL-2.0+
+ * @noinspection      PhpUndefinedFunctionInspection
+ * @noinspection      PhpUndefinedConstantInspection
  *
  * @wordpress-plugin
  * Plugin Name: Fix 'Plugin file does not exist.' Notices
  * Plugin URI: https://wordpress.org/plugins/fix-plugin-does-not-exist-notices/
  * Description: Adds missing plugins to the plugins list with a "Remove Reference" link so you can permanently clean up invalid plugin entries and remove error notices.
- * Version: 1.6.2
+ * Version: 1.6.4
  * Author: Marcus Quinn
  * Author URI: https://www.wpallstars.com
  * License: GPL-2.0+
@@ -46,7 +48,7 @@ if ( ! defined( 'ABSPATH' ) ) {
 }
 
 // Define plugin constants
-define( 'FPDEN_VERSION', '1.6.2' );
+define( 'FPDEN_VERSION', '1.6.4' );
 define( 'FPDEN_PLUGIN_DIR', plugin_dir_path( __FILE__ ) );
 define( 'FPDEN_PLUGIN_URL', plugin_dir_url( __FILE__ ) );
 define( 'FPDEN_PLUGIN_FILE', __FILE__ );
@@ -191,6 +193,7 @@ class Fix_Plugin_Does_Not_Exist_Notices {
 	 * @param array  $plugin_data An array of plugin data.
 	 * @param string $context     The plugin context (e.g., 'all', 'active', 'inactive').
 	 * @return array The potentially modified array of plugin action links.
+	 * @noinspection PhpUnusedParameterInspection
 	 */
 	public function add_remove_reference_action( $actions, $plugin_file, $plugin_data, $context ) {
 		// Only run on the plugins page.
@@ -408,7 +411,7 @@ if (file_exists($autoloader)) {
     require_once $autoloader;
 
     // Initialize the updater if the class exists
-    if (class_exists('\WPAllStars\FixPluginDoesNotExistNotices\Updater')) {
-        new \WPAllStars\FixPluginDoesNotExistNotices\Updater(__FILE__);
+    if (class_exists('\WPALLSTARS\FixPluginDoesNotExistNotices\Updater')) {
+        new \WPALLSTARS\FixPluginDoesNotExistNotices\Updater(__FILE__);
     }
 }

includes/Updater.php

@@ -3,9 +3,11 @@
  * Plugin Updater
  *
  * @package FixPluginDoesNotExistNotices
+ * @noinspection PhpUndefinedFunctionInspection
+ * @noinspection PhpUndefinedClassInspection
  */
 
-namespace WPAllStars\FixPluginDoesNotExistNotices;
+namespace WPALLSTARS\FixPluginDoesNotExistNotices;
 
 /**
  * Class Updater
@@ -76,10 +78,11 @@ class Updater {
      * Check if the plugin was installed from GitHub
      *
      * @return bool
+     * @noinspection PhpUndefinedFunctionInspection
      */
     private function is_github_installation() {
         // Check for GitHub-specific markers in the plugin directory
-        $plugin_dir = plugin_dir_path($this->plugin_file);
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
 
         // Look for .git directory with GitHub remote
         if (file_exists($plugin_dir . '.git')) {
@@ -101,10 +104,11 @@ class Updater {
      * Check if the plugin was installed from Gitea
      *
      * @return bool
+     * @noinspection PhpUndefinedFunctionInspection
      */
     private function is_gitea_installation() {
         // Check for Gitea-specific markers in the plugin directory
-        $plugin_dir = plugin_dir_path($this->plugin_file);
+        $plugin_dir = \plugin_dir_path($this->plugin_file);
 
         // Look for .git directory with Gitea remote
         if (file_exists($plugin_dir . '.git')) {
@@ -121,6 +125,8 @@ class Updater {
      * Initialize Git Updater Lite
      *
      * @return void
+     * @noinspection PhpUndefinedFunctionInspection
+     * @noinspection PhpUndefinedClassInspection
      */
     private function init_git_updater() {
         // Check if the Git Updater Lite class exists (composer autoload)
@@ -135,9 +141,11 @@ class Updater {
         }
 
         // Set the update server based on the installation source
-        add_filter('gul_update_server', function() {
-            if ($this->source === 'github' || $this->source === 'gitea') {
-                return 'https://git-updater.wpallstars.com'; // Update server for both GitHub and Gitea
+        \add_filter('gul_update_server', function() {
+            if ($this->source === 'github') {
+                return 'https://github.com/wpallstars/fix-plugin-does-not-exist-notices'; // GitHub repository URL
+            } elseif ($this->source === 'gitea') {
+                return 'https://gitea.wpallstars.com/wpallstars/fix-plugin-does-not-exist-notices'; // Gitea repository URL
             }
             return '';
         });

languages/fix-plugin-does-not-exist-notices.pot

@@ -2,14 +2,14 @@
 # This file is distributed under the GPL-2.0+.
 msgid ""
 msgstr ""
-"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.2\n"
+"Project-Id-Version: Fix 'Plugin file does not exist.' Notices 1.6.4\n"
 "Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/fix-plugin-does-not-exist-notices\n"
 "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
 "Language-Team: LANGUAGE <LL@li.org>\n"
 "MIME-Version: 1.0\n"
 "Content-Type: text/plain; charset=UTF-8\n"
 "Content-Transfer-Encoding: 8bit\n"
-"POT-Creation-Date: 2024-05-15T12:00:00+00:00\n"
+"POT-Creation-Date: 2024-05-16T12:00:00+00:00\n"
 "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
 "X-Generator: WP-CLI 2.8.1\n"
 "X-Domain: fix-plugin-does-not-exist-notices\n"

readme.txt

@@ -5,7 +5,7 @@ Tags: plugins, missing plugins, cleanup, error fix, admin tools, plugin file doe
 Requires at least: 5.0
 Tested up to: 6.4
 Requires PHP: 7.0
-Stable tag: 1.6.2
+Stable tag: 1.6.4
 License: GPL-2.0+
 License URI: https://www.gnu.org/licenses/gpl-2.0.html
 
@@ -89,12 +89,24 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 
 == Changelog ==
 
+= 1.6.4 =
+* Updated version management to ensure consistent patch version increments
+* Improved documentation for version update process
+* Enhanced AI workflow files with detailed version increment instructions
+
+= 1.6.3 =
+* Fixed Git Updater repository URLs to use full repository paths
+* Corrected Update URI configuration for proper update detection
+* Improved version management following semantic versioning
+* Updated organization name from 'WP All Stars' to 'WP ALLSTARS'
+* Updated namespace from 'WPAllStars' to 'WPALLSTARS'
+
 = 1.6.2 =
 * Updated POT file version for consistency
 * Improved JavaScript localization with proper fallbacks
 * Enhanced code quality for WordPress.org submission
-* Fixed Git Updater configuration with correct Update URI
-* Improved update server URL configuration
+* Added Git Updater configuration with Update URI
+* Added update server URL configuration
 
 = 1.6.1 =
 * Added AI assistant guide and workflow documentation
@@ -184,8 +196,14 @@ Although this plugin consumes minimal disk space, and doesn't run unless you are
 
 == Upgrade Notice ==
 
+= 1.6.4 =
+Improved version management with consistent patch version increments and enhanced documentation for development workflows!
+
+= 1.6.3 =
+Fixed Git Updater repository URLs and updated organization naming for consistent branding across all platforms!
+
 = 1.6.2 =
-Improved JavaScript localization, enhanced code quality, and fixed Git Updater configuration for seamless updates!
+Improved JavaScript localization, enhanced code quality, and added Git Updater configuration for seamless updates!
 
 = 1.6.1 =
 Added comprehensive AI assistant guide and workflow documentation for improved development processes!