Skip to content

fix(payments-next): Upgrading subscription set to cancel does not unset cancelled_for_customer_at#20272

Merged
elizabeth-ilina merged 1 commit intomainfrom
PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at
Mar 31, 2026
Merged

fix(payments-next): Upgrading subscription set to cancel does not unset cancelled_for_customer_at#20272
elizabeth-ilina merged 1 commit intomainfrom
PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at

Conversation

@elizabeth-ilina
Copy link
Copy Markdown
Contributor

@elizabeth-ilina elizabeth-ilina commented Mar 26, 2026

Because

  • When upgrading a subscription that has previously been set to cancel but has not cancelled yet, the metadata field cancelled_for_customer_at is not unset even though we uncancel the subscription as part of the upgrade process.

This pull request

  • Removes cancelled_for_customer_at metadata on subscription upgrade.

Issue that this pull request solves

Closes #PAY-3586

Checklist

Put an x in the boxes that apply

  • My commit is GPG signed.
  • If applicable, I have modified or added tests which pass locally.
  • I have added necessary documentation (if appropriate).
  • I have verified that my changes render correctly in RTL (if appropriate).
  • I have manually reviewed all AI generated code.

How to review (Optional)

  • Key files/areas to focus on:
  • Suggested review order:
  • Risky or complex parts:

Screenshots (Optional)

Cancelled:
image

Then upgraded (no more cancelled_for_customer_at in the metadata):
image

Other information (Optional)

Any other information that is important to this pull request.

@elizabeth-ilina elizabeth-ilina marked this pull request as ready for review March 26, 2026 20:42
@elizabeth-ilina elizabeth-ilina requested a review from a team as a code owner March 26, 2026 20:42
@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at branch 2 times, most recently from fac343d to 7a7b095 Compare March 26, 2026 21:01

const updatedMetadata = {
...subscription.metadata,
cancelled_for_customer_at: '',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be left as-is -- we're not updating auth anymore

@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at branch 2 times, most recently from 07b36b0 to 91e7879 Compare March 30, 2026 19:27
…et cancelled_for_customer_at

Because:

* When upgrading a subscription that has previously been set to cancel but has not cancelled yet, the metadata field cancelled_for_customer_at is not unset even though we uncancel the subscription as part of the upgrade process.

This commit:

* Removes cancelled_for_customer_at on subscription upgrade.

Closes #[PAY-3586](https://mozilla-hub.atlassian.net/browse/PAY-3586)
@elizabeth-ilina elizabeth-ilina force-pushed the PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at branch from 91e7879 to 5add7f5 Compare March 30, 2026 19:29
@elizabeth-ilina elizabeth-ilina merged commit 0ea27ae into main Mar 31, 2026
21 checks passed
@elizabeth-ilina elizabeth-ilina deleted the PAY-3586-upgrading-subscription-set-to-cancel-does-not-unset-cancelled-for-customer-at branch March 31, 2026 16:09
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.

2 participants