Fix paid media in media group failing to send

.github/workflows/test.yml

@@ -12,14 +12,14 @@ jobs:
     name: Test
     runs-on: ubuntu-latest
     steps:
-    - name: Set up Go 1.x
-      uses: actions/setup-go@v2
+    - name: Set up Go 1.23
+      uses: actions/setup-go@v5
       with:
-        go-version: ^1.15
+        go-version: "1.23"
       id: go
 
     - name: Check out code into the Go module directory
-      uses: actions/checkout@v2
+      uses: actions/checkout@v4
 
     - name: Build
       run: go build -v .

.gitignore

@@ -2,3 +2,4 @@
 coverage.out
 tmp/
 book/
+.vscode/

CODEOWNERS

@@ -0,0 +1 @@
+* @iamwavecut @zhuk-kk

README.md

@@ -1,121 +1,117 @@
-# Golang bindings for the Telegram Bot API
+# Golang Bindings for the Telegram Bot API
+[![Go Reference](https://pkg.go.dev/badge/github.com/OvyFlash/telegram-bot-api.svg)](https://pkg.go.dev/github.com/OvyFlash/telegram-bot-api)
+[![Test](https://github.com/OvyFlash/telegram-bot-api/actions/workflows/test.yml/badge.svg)](https://github.com/OvyFlash/telegram-bot-api/actions/workflows/test.yml)
 
-[![Go Reference](https://pkg.go.dev/badge/github.com/go-telegram-bot-api/telegram-bot-api/v5.svg)](https://pkg.go.dev/github.com/go-telegram-bot-api/telegram-bot-api/v5)
-[![Test](https://github.com/go-telegram-bot-api/telegram-bot-api/actions/workflows/test.yml/badge.svg)](https://github.com/go-telegram-bot-api/telegram-bot-api/actions/workflows/test.yml)
+# Headline
 
-All methods are fairly self-explanatory, and reading the [godoc](https://pkg.go.dev/github.com/go-telegram-bot-api/telegram-bot-api/v5) page should
-explain everything. If something isn't clear, open an issue or submit
-a pull request.
+This is a maintained fork of go-telegram-bot-api that preserves the original design while staying current with the latest Telegram Bot API specifications. It continues the development of the original [github.com/go-telegram-bot-api](https://github.com/go-telegram-bot-api/telegram-bot-api) package.
 
-There are more tutorials and high-level information on the website, [go-telegram-bot-api.dev](https://go-telegram-bot-api.dev).
+## Features
 
-The scope of this project is just to provide a wrapper around the API
-without any additional features. There are other projects for creating
-something with plugins and command handlers without having to design
-all that yourself.
+- Complete coverage of the Telegram Bot API
+- Simple and intuitive interface
+- Minimal dependencies
+- Production-ready and actively maintained
+- Preserves original API structure for easy migration
 
-Join [the development group](https://telegram.me/go_telegram_bot_api) if
-you want to ask questions or discuss development.
+## Installation
 
-## Example
-
-First, ensure the library is installed and up to date by running
-`go get -u github.com/go-telegram-bot-api/telegram-bot-api/v5`.
-
-This is a very simple bot that just displays any gotten updates,
-then replies it to that chat.
-
-```go
-package main
-
-import (
-	"log"
-
-	tgbotapi "github.com/go-telegram-bot-api/telegram-bot-api/v5"
-)
-
-func main() {
-	bot, err := tgbotapi.NewBotAPI("MyAwesomeBotToken")
-	if err != nil {
-		log.Panic(err)
-	}
-
-	bot.Debug = true
-
-	log.Printf("Authorized on account %s", bot.Self.UserName)
-
-	u := tgbotapi.NewUpdate(0)
-	u.Timeout = 60
-
-	updates := bot.GetUpdatesChan(u)
+Install the latest version:
+```bash
+go get -u github.com/OvyFlash/telegram-bot-api
+```
 
-	for update := range updates {
-		if update.Message != nil { // If we got a message
-			log.Printf("[%s] %s", update.Message.From.UserName, update.Message.Text)
 
-			msg := tgbotapi.NewMessage(update.Message.Chat.ID, update.Message.Text)
-			msg.ReplyToMessageID = update.Message.MessageID
+> ❗ Tag versioning is discouraged due to the unstable nature of the Telegram Bot API, and it might break at any time after the API changes.
+> ~~`go get -u github.com/OvyFlash/telegram-bot-api/v7`~~
 
-			bot.Send(msg)
-		}
-	}
-}
-```
+## Quick Start
 
-If you need to use webhooks (if you wish to run on Google App Engine),
-you may use a slightly different method.
+Here's a simple echo bot using polling:
 
 ```go
 package main
 
 import (
-	"log"
-	"net/http"
-
-	"github.com/go-telegram-bot-api/telegram-bot-api/v5"
+    "log"
+    "time"
+    api "github.com/OvyFlash/telegram-bot-api"
 )
 
 func main() {
-	bot, err := tgbotapi.NewBotAPI("MyAwesomeBotToken")
-	if err != nil {
-		log.Fatal(err)
-	}
+    bot, err := api.NewBotAPI("BOT_TOKEN")
+    if err != nil {
+        panic(err)
+    }
 
-	bot.Debug = true
+    log.Printf("Authorized on account %s", bot.Self.UserName)
 
-	log.Printf("Authorized on account %s", bot.Self.UserName)
+    updateConfig := api.NewUpdate(0)
+    updateConfig.Timeout = 60
+    updatesChannel := bot.GetUpdatesChan(updateConfig)
 
-	wh, _ := tgbotapi.NewWebhookWithCert("https://www.example.com:8443/"+bot.Token, "cert.pem")
+    // Optional: Clear initial updates
+    time.Sleep(time.Millisecond * 500)
+    updatesChannel.Clear()
 
-	_, err = bot.Request(wh)
-	if err != nil {
-		log.Fatal(err)
-	}
+    for update := range updatesChannel {
+        if update.Message == nil {
+            continue
+        }
 
-	info, err := bot.GetWebhookInfo()
-	if err != nil {
-		log.Fatal(err)
-	}
+        log.Printf("[%s] %s", update.Message.From.UserName, update.Message.Text)
 
-	if info.LastErrorDate != 0 {
-		log.Printf("Telegram callback failed: %s", info.LastErrorMessage)
-	}
+        msg := api.NewMessage(update.Message.Chat.ID, update.Message.Text)
+        msg.ReplyParameters.MessageID = update.Message.MessageID
 
-	updates := bot.ListenForWebhook("/" + bot.Token)
-	go http.ListenAndServeTLS("0.0.0.0:8443", "cert.pem", "key.pem", nil)
-
-	for update := range updates {
-		log.Printf("%+v\n", update)
-	}
+        bot.Send(msg)
+    }
 }
 ```
 
-If you need, you may generate a self-signed certificate, as this requires
-HTTPS / TLS. The above example tells Telegram that this is your
-certificate and that it should be trusted, even though it is not
-properly signed.
+## Webhook Setup
 
+For webhook implementation:
+1. Check the [examples](./examples) folder for examples of webhook implementations
+2. Use HTTPS (required by Telegram)
+   - Generate SSL certificate:
+    ```bash
     openssl req -x509 -newkey rsa:2048 -keyout key.pem -out cert.pem -days 3560 -subj "//O=Org\CN=Test" -nodes
-
-Now that [Let's Encrypt](https://letsencrypt.org) is available,
-you may wish to generate your free TLS certificate there.
+    ```
+   - Bring your own SSL certificate. [Let's Encrypt](https://letsencrypt.org) is recommended for free TLS certificates in production.
+
+## Documentation
+
+- [GoDoc](https://pkg.go.dev/github.com/OvyFlash/telegram-bot-api)
+- Check the [examples](./examples) directory for more use cases
+
+
+## Contributing
+
+- Issues and feature requests are welcome
+- Pull requests should maintain the existing design philosophy
+- The focus is on providing a clean API wrapper without additional features
+
+## License
+
+>The [MIT License](./LICENSE.txt)
+>
+>Copyright (c) 2015 Syfaro
+>
+>Permission is hereby granted, free of charge, to any person obtaining a copy
+>of this software and associated documentation files (the "Software"), to deal
+>in the Software without restriction, including without limitation the rights
+>to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+>copies of the Software, and to permit persons to whom the Software is
+>furnished to do so, subject to the following conditions:
+>
+>The above copyright notice and this permission notice shall be included in all
+>copies or substantial portions of the Software.
+>
+>THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+>IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+>FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+>AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+>LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+>OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+>SOFTWARE.