build(deps): bump github.com/go-telegram/bot from 1.22.0 to 1.23.0 in the go-minor group

[dependabot]

Bumps the go-minor group with 1 update: github.com/go-telegram/bot.

Updates github.com/go-telegram/bot from 1.22.0 to 1.23.0

Release notes

Sourced from github.com/go-telegram/bot's releases.

v1.23.0

• Support Bot API 10.2 (July 14, 2026 update):
  • Rich Messages: new InputRichMessageMedia, InputMediaVoiceNote, the 21 InputRichBlock* block types (via the InputRichBlock tagged union) and InputRichBlockListItem; added blocks and media fields to InputRichMessage.
  • Ephemeral Messages: new methods editEphemeralMessageText, editEphemeralMessageMedia, editEphemeralMessageCaption, editEphemeralMessageReplyMarkup, deleteEphemeralMessage; added receiver_user_id and callback_query_id params to the 13 send methods; is_ephemeral on BotCommand; receiver_user and ephemeral_message_id on Message; ephemeral_message_id on ReplyParameters (and message_id made optional).
  • Communities: new Community, CommunityChatAdded, CommunityChatRemoved; community_chat_added / community_chat_removed on Message; community on ChatFullInfo.
  • General: new BotSubscriptionUpdated with the subscription field on Update (and subscription allowed-update constant).
• Fix: InputMedia values now implement json.Marshaler, so the required type discriminator is kept when they are encoded through a plain json.Marshal (e.g. nested inside a rich message). Previously type was only emitted by MarshalInputMedia, which nested values never reached.
• Fix: MarshalJSON on the InputRichBlock, RichBlock and RichText tagged unions returns an error instead of panicking when Type is set without its matching variant pointer, and reports an unknown Type as unsupported rather than as a missing variant.
• Fix: marshaling those unions no longer writes the discriminator back into the caller's variant. The type field is stamped on a copy, so encoding has no side effects and the same value can be encoded from several goroutines.
• Fix: EditMessageCaptionParams.ShowCaptionAboveMedia was sent under the field name k instead of show_caption_above_media, so it never took effect.

Changelog

Sourced from github.com/go-telegram/bot's changelog.

v1.23.0 (2026-08-03)

• Support Bot API 10.2 (July 14, 2026 update):
  • Rich Messages: new InputRichMessageMedia, InputMediaVoiceNote, the 21 InputRichBlock* block types (via the InputRichBlock tagged union) and InputRichBlockListItem; added blocks and media fields to InputRichMessage.
  • Ephemeral Messages: new methods editEphemeralMessageText, editEphemeralMessageMedia, editEphemeralMessageCaption, editEphemeralMessageReplyMarkup, deleteEphemeralMessage; added receiver_user_id and callback_query_id params to the 13 send methods; is_ephemeral on BotCommand; receiver_user and ephemeral_message_id on Message; ephemeral_message_id on ReplyParameters (and message_id made optional).
  • Communities: new Community, CommunityChatAdded, CommunityChatRemoved; community_chat_added / community_chat_removed on Message; community on ChatFullInfo.
  • General: new BotSubscriptionUpdated with the subscription field on Update (and subscription allowed-update constant).
• Fix: InputMedia values now implement json.Marshaler, so the required type discriminator is kept when they are encoded through a plain json.Marshal (e.g. nested inside a rich message). Previously type was only emitted by MarshalInputMedia, which nested values never reached.
• Fix: MarshalJSON on the InputRichBlock, RichBlock and RichText tagged unions returns an error instead of panicking when Type is set without its matching variant pointer, and reports an unknown Type as unsupported rather than as a missing variant.
• Fix: marshaling those unions no longer writes the discriminator back into the caller's variant. The type field is stamped on a copy, so encoding has no side effects and the same value can be encoded from several goroutines.
• Fix: EditMessageCaptionParams.ShowCaptionAboveMedia was sent under the field name k instead of show_caption_above_media, so it never took effect.

Commits

• d7672bb fix: make tagged-union marshaling side-effect free, fix show_caption_above_media
• d47ba91 feat: support Bot API 10.2 (Ephemeral Messages, rich blocks, Communities) (#288)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[DuckBugAgent]

Раунд 1 из 3 · полное ревью · Совместимость API и целостность go.sum

Ревью

Замечаний по изменениям не нашёл.

• Коротко: Чистый minor-бамп go-telegram/bot 1.22.0 → 1.23.0: хеши go.sum сверены с апстримом, все изменения API аддитивны и код репозитория не затрагивают.
• Риски/вопросы:
  • Проверка «Lint & Tests» на head SHA всё ещё pending — это единственный гейт, который компилирует тесты. Успешный «Build telegram image» ничего о них не говорит: adapters/telegram/Dockerfile собирает только go build ./cmd/flock-telegram, то есть нетестовый код. Тестовые файлы я проверил статически (все композитные литералы моделей — с именами полей, unkeyed-литералов нет), так что аддитивные поля их сломать не могут, но фактический результат прогона на момент ревью неизвестен.
  • Наблюдение вне рамок этого PR (бамп его НЕ ломает, отдельной задачей): комментарий в adapters/telegram/richtransport.go:32 утверждает, что «go-telegram/bot v1.21.0 (the latest) does not expose them» — обоснование существования HTTP-шима. Фактически метод SendRichMessage есть в библиотеке уже в v1.22.0 (methods.go:1118), то есть комментарий устарел ещё до этого PR. Шим продолжает работать (он ходит своим HTTP и использует локальный тип inputRichMessage), но условие «removed once the lib models the rich methods natively» из его же комментария выполнено — имеет смысл завести отдельный тикет на переход на нативный метод.
  • ReplyParameters.MessageID получил omitempty (был json:"message_id"). Поведенческая разница возникает только при MessageID == 0, а в этом коде replyToID приходит из strconv.Itoa(msg.ID) и на вызове в core/chat/service.go:916 защищён проверкой answerMsgID != "", поэтому нуля там не бывает. Влияния на adapters/telegram/bot.go:133 нет.

---

Арбитр ревью: остановлено — блокирующего не осталось, PR готов к мерджу человеком.

Причина: Раунд 1 из 3, ревьювер вернул вердикт ok без единой находки: чистый minor-бамп go-telegram/bot 1.22.0 → 1.23.0 с аддитивными изменениями API, код репозитория не затронут. Блокирующего (BLOCKER/MAJOR/MINOR) нет — держать PR нечем.