docs: write the v0.4.20 release notes - #96
Merged
Conversation
The release tag job refused v0.4.20 because RELEASE.md still opened with the v0.4.19 notes, which is exactly the check that distinguishes notes written for this release from the previous release's leftovers. Covers what shipped: server-verified Stripe capture, serialized checkout capture, customer update authorization, the QPay callback URL fix, and cash pickup without a delivery quote. Upgrade steps call out the new checkouts migration, the core-api v1.6.60 floor the QPay callback needs, and the two client-facing contract changes.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #96 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 1775 1775
===========================================
Files 135 135
Lines 7785 7785
===========================================
Hits 7785 7785
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Why CI failed
The Release Tag run on the #91 merge failed its notes validation:
RELEASE.mdstill held the v0.4.19 notes — which is precisely the check that tells notes written for this release from the previous release's leftovers. No tag was pushed, sov0.4.20does not exist yet.What this PR does
Replaces
RELEASE.mdwith notes for what actually shipped in v0.4.20 (#90, #92, #93, #94, #95), keeping the established structure:409on a concurrent attempt, existing order on a repeat),Customer-Tokenownership on profile updates, the malformed QPay cancel/refund callback URL.capture-qpayroute and carries the per-checkout URL, the402/422/502capture contract, cash pickup without a delivery quote, the persisted PaymentIntent, and the QPay token-caching / product-query wins.checkouts.stripe_payment_intent_idmigration, the core-api v1.6.60 floor (the QPay callback depends on theUtils::apiUrlquery-string fix from Bugfix: Utils::apiUrl renders query params as path segments core-api#248), and the two client-facing contract changes: confirm the PaymentIntent before capture, and sendCustomer-Tokenwhen updating a customer.Validation
Simulated the reusable workflow's three checks against this branch:
v0.4.20✅ —> v0.4.20 ~ "Verified payments and gateway callbacks that arrive"RELEASE_NOTES_PLACEHOLDER✅composer.json,package.json,extension.jsonall read0.4.20✅After merge
This branch is not
dev-v*, so merging it will not auto-trigger the tag workflow. Per the recovery path documented in.github/workflows/release.yml, tag it with a manual dispatch once this lands:Note that pushing
v0.4.20chains intocreate-release.ymland the npm/GitHub publish jobs.