Skip to content
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

Regression: Restore cancel_at being set for new subscriptions #1437

Closed
chrisjsimpson opened this issue Jan 22, 2025 · 33 comments
Closed

Regression: Restore cancel_at being set for new subscriptions #1437

chrisjsimpson opened this issue Jan 22, 2025 · 33 comments
Labels
released This issue/pull request has been released.

Comments

@chrisjsimpson
Copy link
Contributor

Is your feature request related to a problem? Please describe.

A refactor in update_subscription statuses, caused cancel_at not being set on new plans if this setting was chosen (and missing test which exists , @516_subscriber_order_plan_with_cancel_at but was missing from automated test runs).

Describe the solution you'd like

  • restore cancel_at and include test in test run.

Describe alternatives you've considered

Additional context

TODO add consistency to test run naming so that inclusion of all existing tests may be valitated automatically (missing no tests).

Copy link

🚀 Issue was released in v0.1.225 🚀

6 similar comments
Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

@github-actions github-actions bot added the released This issue/pull request has been released. label Jan 22, 2025
Copy link

🚀 Issue was released in v0.1.225 🚀

11 similar comments
Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

13 similar comments
Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Copy link

🚀 Issue was released in v0.1.225 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released This issue/pull request has been released.
Projects
None yet
Development

No branches or pull requests

1 participant