wpallstars/wp-fix-plugin-does-not-exist-notices
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 15 Wiki Activity

Version 2.2.2-stable - Cleanup and improvements

Browse Source
This commit is contained in:
Marcus Quinn
2025-04-14 22:28:37 +01:00
parent c73964888b
commit e4c70b5711
9 changed files with 54 additions and 508 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
.ai-workflows/README.md
View File

@ -7,6 +7,7 @@ This directory contains workflow documentation for AI assistants working with th
- **bug-fixing.md**: Guidelines for identifying and fixing bugs in the codebase
- **code-review.md**: Standards and procedures for reviewing code changes
- **feature-development.md**: Process for developing new features
- **local-env-vars.md**: Local development environment paths and URLs
- **release-process.md**: Steps for preparing and publishing new releases
These documents help ensure consistent quality and approach when using AI tools to assist with development tasks.

12
.ai-workflows/release-process.md
View File

@ -63,13 +63,15 @@ new WPALLSTARS\FixPluginDoesNotExistNotices\Plugin(__FILE__, '{MAJOR}.{MINOR}.{P
#### b. JavaScript Files with Version Constants
Check for any JavaScript files that contain version constants, such as `admin/js/version-fix.js`:
Check for any JavaScript files that might contain version constants:
```javascript
// Current plugin version - this should match the version in the main plugin file
const CURRENT_VERSION = '{MAJOR}.{MINOR}.{PATCH}';
```
**Note**: As of version 2.2.1, we've removed redundant JavaScript files like `version-fix.js` since Git Updater now correctly detects the version from the main branch.
#### c. CHANGELOG.md
Add a new section at the top of the CHANGELOG.md file:
@ -170,9 +172,11 @@ https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/releases
If the release doesn't appear or doesn't have the ZIP file attached, check the GitHub Actions page:
https://github.com/wpallstars/wp-fix-plugin-does-not-exist-notices/actions
### 8. Merge to Main (When Ready)
### 8. Merge to Main (CRITICAL STEP)
When you're satisfied with the release, merge the feature branch to main:
**IMPORTANT**: This step is critical for Git Updater to detect the new version. Git Updater reads the readme.txt file from the main branch, not from tags or releases.
Merge the feature branch to main immediately after pushing the tag:
```bash
git checkout main
@ -183,6 +187,8 @@ git push gitea main
The `--no-ff` flag creates a merge commit even if a fast-forward merge is possible, which helps preserve the branch history.
**Note**: Only use named branches like feature/*, fix/*, etc. for development. Release branches (v*) should always be merged to main immediately after tagging to ensure Git Updater can detect the new version.
### 9. Verify Release
- [ ] Check that the GitHub release was created successfully with the ZIP file attached