|
| 1 | +--- |
| 2 | +name: 💥 BC Break |
| 3 | +about: Have you encountered an issue during an upgrade? 💣 |
| 4 | +labels: bc break |
| 5 | +--- |
| 6 | + |
| 7 | +<!-- |
| 8 | +Before reporting a BC break, please consult the changelog and wiki entry for the particular version to make sure it's not an expected change: |
| 9 | +- https://github.com/php-telegram-bot/telegram-bot-manager/blob/master/CHANGELOG.md |
| 10 | +- https://github.com/php-telegram-bot/telegram-bot-manager/wiki/Breaking-backwards-compatibility |
| 11 | +--> |
| 12 | + |
| 13 | +### BC Break Report |
| 14 | + |
| 15 | +<-- |
| 16 | +❗ NEVER put your Telegram API key or any other private details here. (like passwords, user IDs, etc.) |
| 17 | +Substitute them like <API_KEY> or <USER_ID> etc. |
| 18 | +--> |
| 19 | + |
| 20 | +#### Required Information |
| 21 | + |
| 22 | +<!-- Fill in the relevant information below to help triage your pull request. --> |
| 23 | +<!-- Please enter exact version numbers, not just "latest" etc.! --> |
| 24 | + |
| 25 | +| ? | ! |
| 26 | +| --- | --- |
| 27 | +| Operating system | Name and version |
| 28 | +| PHP Telegram Bot Manager version | x.y.z |
| 29 | +| PHP Telegram Bot version | x.y.z |
| 30 | +| PHP version | x.y.z |
| 31 | +| MySQL version | x.y.z / none |
| 32 | +| Update Method | Webhook / getUpdates |
| 33 | +| Self-signed certificate | yes / no |
| 34 | +| RAW update (if available) | `{...}` |
| 35 | + |
| 36 | +#### Summary |
| 37 | + |
| 38 | +<!-- Provide a summary describing the problem you are experiencing. --> |
| 39 | + |
| 40 | +#### Previous behaviour |
| 41 | + |
| 42 | +<!-- What was the previous (working) behaviour? --> |
| 43 | + |
| 44 | +#### Current behaviour |
| 45 | + |
| 46 | +<!-- What is the current (broken) behaviour? --> |
| 47 | + |
| 48 | +#### How to reproduce |
| 49 | + |
| 50 | +<!-- |
| 51 | +Provide steps to reproduce the bug. |
| 52 | +If possible, also add any relevant code snippet. |
| 53 | +--> |
| 54 | + |
| 55 | +#### Expected behaviour |
| 56 | + |
| 57 | +<!-- What was the expected (correct) behaviour? --> |
0 commit comments