-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Alpha release Dec 12 #3625
Merged
Merged
Alpha release Dec 12 #3625
Conversation
This file contains 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
… renewals (#3525) This PR adds handling for a new `my-account/renew-subscription` endpoint to redirect readers to the first available pending renewal checkout, otherwise the subscriptions my account page.
* feat(wc): duplicate orders admin notice * feat: handle HPOS * feat: handle order series dismissal * feat: better UX with a details element * feat: iterate orders instead of using a direct DB query * chore: unify wording * fix: handle the order meta * feat: CLI tool * feat: process orders in batches * feat: tweak
This PR adds meta data to cancelled woo subscriptions and uses this new meta to sync cancellation reason to ESPs for cancelled subscriptions.
This PR adds a cli command to migrate the status of all on-hold subscriptions that have failed all retries to expired
This PR updates the subscriptions expiration feature by: - Adding expired cancellation reason meta value - Adding a filter to the is_enabled WCS integration method - Updating the default on-hold duration to 30 days
This removes the NEWSPACK_SUBSCRIPTIONS_EXPIRATION feature flag.
* fix(ras): do not require Woo plugins if using NRH * fix: check for Atomic site ID in plugin install message * refactor: use Manager helper method for checking Atomic hosted status
This updates the `wp newspack migrate-expired-subscription` command behavior to schedule a final retry when the last retry took place within the sites on-hold duration.
🎉 This PR is included in version 5.10.0-alpha.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 5.10.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
A new alpha release.