Release v1.3.0

[github-actions]

What does this change?

This PR bumps the plugin version to v1.3.0 and introduces critical bug fixes, architectural improvements, and developer experience enhancements.

Core Fixes & Improvements:

• API Singleton Logic: Resolved a bug where the API singleton incorrectly cached or returned credentials, causing conflicts on sites using a mix of Global and Form-specific configurations.
• Payment Completion Fix: Corrected the rgar() argument order within complete_payment(). This fixes a regression where "Delayed Feeds" (e.g., Mailchimp, post creation, or other add-ons) failed to trigger after a successful payment.
• Error Handling: Enhanced the API client with robust WP_Error and HTTP status code handling to improve failure diagnostics and logging.
• Credential Management: Introduced get_credentials_for_feed() to centralize and standardize how credentials are resolved across various payment flows.

Developer & CI/CD Updates:

• CI/CD Modernization:
  • Added PHP 8.5 to the compatibility matrix.
  • Improved release logic in prepare-release.yml to support legacy tag patterns (gravity-forms-upload-v*).
  • Updated plugin-check.yml to better handle transient environment timeouts.
• Documentation: Added CONTRIBUTING.md and CLAUDE.md.
• Repository Cleanup: Removed composer.lock from version tracking to minimize merge conflicts and allow for flexible dependency resolution in development.
• Compatibility & Metadata:
  • Bumped "Tested up to" version for WordPress 7.0.
  • Updated Author URI to use HTTPS (https://www.chip-in.asia).
  • Added .wordpress-org/ directory for hosting assets like banners and icons on the WordPress Plugin Directory.

How to test

1. Version Verification: Confirm chip-for-gravity-forms.php, package.json, readme.txt, and changelog.txt all reflect version 1.3.0.
2. Credential Resolution: Configure a form with specific CHIP credentials different from the Global settings. Process a test transaction to ensure the correct keys are utilized (verifying the API singleton and get_credentials_for_feed logic).
3. Payment Flow & Delayed Feeds: Complete a transaction and verify that "Delayed Feeds" (e.g., Gravity Forms Mailchimp or User Registration add-ons) trigger correctly. This verifies the rgar() argument order fix.
4. CI/CD Logic: Ensure the GitHub Action prepare-release.yml correctly identifies the previous tag using the updated regex/sort logic.
5. Unit Tests: Run the newly added test suite covering credentials, callbacks, and timezone handling.

Potential Risks & Review Items

• Credential Resolution Logic: get_credentials_for_feed() is now a central helper. Reviewers should ensure it handles edge cases (e.g., missing keys or malformed feed objects) gracefully.
• Composer Tracking: Removing composer.lock means subsequent builds will rely on composer.json constraints. We must ensure internal build processes are compatible with this change to prevent "works on my machine" issues.
• Payment Completion: The change to rgar() in complete_payment() modifies how data is extracted from the entry/action arrays. While this fixes delayed feeds, it should be verified against other third-party Gravity Forms add-ons to ensure no regressions in data mapping.

Is this PR safe for automatic approval?

No. This release contains critical changes to the payment processing logic, API credential handling, and CI/CD pipelines that require manual verification.

Images

No visual changes to the UI were included in this specific diff, though WP.org assets were added to the repository.

Related Tasks / PRs

• See changelog for all versions

Checklist

• Unit tests provided?
• All tests passing?
• Tested in staging?
• Task link provided?
• Review changelog accuracy
• Verify version bumped in all files
• After merge, create tag v1.3.0 to trigger deploy

[github-actions]

✅ WordPress Plugin Check Report

✅ Status: Passed

📊 Report

All checks passed! No errors or warnings found.

---

🤖 Generated by WordPress Plugin Check Action • Learn more about Plugin Check