Repository navigation
Release v1.5.0 - #65
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release v1.5.0
Version bump only. The changelog below is carried from this branch into
readme.txt(which holds only the shipping release) andchangelog.txt(fullhistory).
Changelog
gform_full_accessrather than the granular settings capability.{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.Version is a MINOR bump
1.4.0->1.5.0. Since the last release the plugin gained two features (thesubscriptions 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 pluginheader,
GF_CHIP_MODULE_VERSION, theStable tagin readme.txt andpackage.json.Notes for the reviewer
that workflow reads
AI_API_KEYandAI_API_URLand both are unset in thisrepository, so it fails at the changelog step before bumping anything. The
changelog here is written from the actual commits in
v1.4.0..maininstead.AI_API_URLis read from repo variables (vars.AI_API_URL) rather thansecrets, so it is not visible with
gh secret list. Whoever sets these needsto set the variable too, or the workflow keeps failing the same way.
readme.txtmust carry exactly one changelog entry; the script replaces theprevious one rather than appending. Verified:
1.4.0no longer appears there.Checklist
GF_CHIP_MODULE_VERSION,Stable tag,package.jsonchangelog.txtandreadme.txtcarry the entryphpunit505 tests / 1021 assertions green, on both the composer-pinned 9.6 and the CI toolchain 12.5phpcsexit 0v1.5.0to trigger the WordPress.org deploy