# Breaking Changes

## How to handle (potential) Breaking Changes?

For every (potential) breaking change you might want to...

* Add *breaking* in the squashed commit description of the pull request on Github\\

  <div align="left"><figure><img src="https://2849746287-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FI94kSPjKj4zHlecmyik1%2Fuploads%2FCLeWi8lgbdBjXR8zC9yo%2Fimage.png?alt=media&#x26;token=62705014-730f-4e02-bb19-1fdafd6371d6" alt="" width="375"><figcaption></figcaption></figure></div>
* Leave a note on the list bellow stating who it will *affect,* how to *migrate and optionally* the *author's* name (can also be seen in the linked pr) and most important the link to the PR on Github.

## List of Breaking Changes

### 2025-02-21 <https://github.com/wepublish/wepublish/pull/1739>

**Affects:** All instances working with Website-Builder and having members

**Migration:** Change *profile/subscription* to */profile* everywhere used. This is most likely in automated e-mails or links.

Special case **Gruppetto:** Please, additionaly change */abo* to */mitmachen*

**Author:** Michael Scheurer

### 2024-11-25 <https://github.com/wepublish/wepublish/pull/1680>

**Affects**: TSRI only

**Migration**: Add monthly target price in the editor for each member plan. the target price is minimal price plus 7 chf.

**Author:** Michael Scheurer

### 2024-11-27 <https://github.com/wepublish/wepublish/pull/1655>

**Affects**: Most instances

**Migration**: Add success and failing urls for each instance within the editor

* Bajour
  * success: /profile/subscription
  * fail: /fail
* Gruppetto
  * success: /payment/success
  * fail: /payment/fail
* Kolumna: currently in discussion. No action needed.
* Mannschaft
  * success: /profile/subscription
  * fail: motivate mannschaft to add a failing-page
* TSRI
  * motivate tsri to add such after-payment-pages
* Zwoelf: No action needed.

**Author:** Michael Scheurer
