Skip to content

Release v1.5.0 - #65

Merged
wzul merged 1 commit into
mainfrom
release/v1.5.0
Sep 25, 2026
Merged

wzul merged 1 commit into
mainfrom
release/v1.5.0

Conversation

@wzul

@wzul wzul commented Sep 25, 2026

Copy link
Copy Markdown
Collaborator

Release v1.5.0

Version bump only. The changelog below is carried from this branch into
readme.txt (which holds only the shipping release) and changelog.txt (full
history).

Changelog

  • Added - The CHIP Subscriptions screen is now a real WordPress list table, with search, bulk actions, screen options for hiding columns, sortable columns and pagination, instead of a hand-built table.
  • Added - A Charge now action that collects a subscription's next payment before it is due, for support cases such as a customer asking to pay early. It asks for confirmation first, because it charges the stored card outside the normal schedule, and it leaves the billing schedule, the installments and the retry ladder untouched.
  • Fixed - A failed renewal no longer sends two emails. The built-in dunning email now stands down when a notification you configured will send for the same event, so a notification on Subscription Payment Failed is the only email the customer receives.
  • Fixed - A failure that exhausts the retry ladder no longer announces two events in one run, so a notification on both Subscription Payment Failed and Subscription Expired will not double up.
  • Fixed - The built-in dunning email is no longer sent once a subscription has expired, where the update-card link it carried had already stopped working. Customers are emailed on the retry attempts before that, while their card can still be updated.
  • Fixed - Retry now names the actual reason it collected nothing, instead of listing every possibility and leaving you to guess. A subscription that is merely not yet due is told its next payment date, and is offered Charge now instead of a retry that cannot work.
  • Fixed - The subscription actions (Send update-card link, retry, cancel) are gated on the same capability as the page that offers them, so they no longer answer "You are not allowed to do that." for administrators and Gravity Forms users, who carry gform_full_access rather than the granular settings capability.
  • Fixed - The Screen Options column preferences on the subscriptions screen are honoured, so hiding a column sticks instead of being silently reset on the next page load.
  • Fixed - A subscription row links to its own entry, rather than to a form entry url that did not exist.
  • Fixed - Send update-card link reports whether the email actually left, instead of reporting success even when the address was refused or the send failed.
  • Changed - Documented how to customise subscription emails: the {chip_update_card_link} merge tag, the three subscription notification events, the plugin's filters, and the Gravity Forms hooks for changing the design, the subject or the sender.
  • Changed - Updated to the PHPUnit configuration schema that CI actually runs, so a passing suite no longer reports a deprecation on every run.

Version is a MINOR bump

1.4.0 -> 1.5.0. Since the last release the plugin gained two features (the
subscriptions screen rebuilt as a list table, and the Charge now action),
so this is not a patch. The version is bumped in one place, by
scripts/bump-version.sh, which is the repo's own tool: it updates the plugin
header, GF_CHIP_MODULE_VERSION, the Stable tag in readme.txt and
package.json.

Notes for the reviewer

  • This PR cannot be produced by the Prepare Release workflow as it stands:
    that workflow reads AI_API_KEY and AI_API_URL and both are unset in this
    repository, so it fails at the changelog step before bumping anything. The
    changelog here is written from the actual commits in v1.4.0..main instead.
  • AI_API_URL is read from repo variables (vars.AI_API_URL) rather than
    secrets, so it is not visible with gh secret list. Whoever sets these needs
    to set the variable too, or the workflow keeps failing the same way.
  • readme.txt must carry exactly one changelog entry; the script replaces the
    previous one rather than appending. Verified: 1.4.0 no longer appears there.

Checklist

  • Version bumped in plugin header, GF_CHIP_MODULE_VERSION, Stable tag, package.json
  • changelog.txt and readme.txt carry the entry
  • phpunit 505 tests / 1021 assertions green, on both the composer-pinned 9.6 and the CI toolchain 12.5
  • phpcs exit 0
  • After merge, tag v1.5.0 to trigger the WordPress.org deploy

@wzul
wzul merged commit b2a638f into main Sep 25, 2026
7 checks passed
@wzul
wzul deleted the release/v1.5.0 branch September 25, 2026 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant