[dependabot]

Bumps the gomod group with 2 updates in the / directory: github.com/FreshLabDev/tg and github.com/jackc/pgx/v5.

Updates github.com/FreshLabDev/tg from 0.0.1-alpha.7 to 0.1.0

Release notes

Sourced from github.com/FreshLabDev/tg's releases.

v0.1.0

The first stable release of the 0.1.0 line, summarising it rather than only the delta since alpha.1.

tg gained the surface searchy needed to leave its third-party client: media sends, inline mode, link-preview control and the chat and action constants that went with them. Nothing that already existed moved, so the three bots already on this module are unaffected by any of it.

Below, the entries added after alpha.1 was tagged. The media and inline work is described in the alpha.1 section.

Added

• docs/releases.md gained a Deploying section, and AGENTS.md points at it. Releasing was documented; deploying was not, in any repository in the family — the process stopped at "deploy it" and never said how. That gap mattered more after the stacks moved from building on the host to pulling a published image, because the procedure changed on the same day. The section names this stack's host directory, its env file, the variable that selects the image, the networks it needs, and what a rollback actually is.

v0.1.0-alpha.1

The surface searchy needs to leave its third-party client. Nothing that existed moved, so every bot already on tg is unaffected; the version says 0.1.0 rather than 0.0.2 because the additions are notable, and carries alpha because no bot has yet run on them against live Telegram.

Added

• Media sends. SendPhoto, SendVideo, SendAudio, SendDocument and SendMediaGroup, plus EditMessageMedia and EditMessageReplyMarkup. A file is an InputFile, and which of the three shapes it takes decides the request on its own: InputFileString for a file_id or an https URL Telegram fetches itself, InputFileLocal for a path on the disk of a server started with --local, and InputFileUpload for bytes — only the last builds a multipart body. A local path sent to Telegram's own endpoint is refused before the request, because the failure it would otherwise produce ("wrong file identifier") points nowhere near the cause.
• Inline mode. AnswerInlineQuery, the InlineQuery and ChosenInlineResult update kinds, and the two result cards the family uses: InlineQueryResultPhoto and InlineQueryResultArticle with InputTextMessageContent. Answering with an empty result list is now expressible, and results is always sent, because an omitted parameter is a 400 rather than "nothing found".
• LinkPreviewOptions as a type, SendTextWithPreview for the one case where a bot relays text whose author wanted the preview, and AnswerCallbackQueryURL for a button that opens a t.me deep link with no intermediate message.

... (truncated)

Changelog

Sourced from github.com/FreshLabDev/tg's changelog.

v0.1.0 - 2026-09-09

The first stable release of the 0.1.0 line, summarising it rather than only the delta since alpha.1.

tg gained the surface searchy needed to leave its third-party client: media sends, inline mode, link-preview control and the chat and action constants that went with them. Nothing that already existed moved, so the three bots already on this module are unaffected by any of it.

Below, the entries added after alpha.1 was tagged. The media and inline work is described in the alpha.1 section.

Added

• docs/releases.md gained a Deploying section, and AGENTS.md points at it. Releasing was documented; deploying was not, in any repository in the family — the process stopped at "deploy it" and never said how. That gap mattered more after the stacks moved from building on the host to pulling a published image, because the procedure changed on the same day. The section names this stack's host directory, its env file, the variable that selects the image, the networks it needs, and what a rollback actually is.

v0.1.0-alpha.1 - 2026-09-09

The surface searchy needs to leave its third-party client. Nothing that existed moved, so every bot already on tg is unaffected; the version says 0.1.0 rather than 0.0.2 because the additions are notable, and carries alpha because no bot has yet run on them against live Telegram.

Added

• Media sends. SendPhoto, SendVideo, SendAudio, SendDocument and SendMediaGroup, plus EditMessageMedia and EditMessageReplyMarkup. A file is an InputFile, and which of the three shapes it takes decides the request on its own: InputFileString for a file_id or an https URL Telegram fetches itself, InputFileLocal for a path on the disk of a server started with --local, and InputFileUpload for bytes — only the last builds a multipart body. A local path sent to Telegram's own endpoint is refused before the request, because the failure it would otherwise produce ("wrong file identifier") points nowhere near the cause.
• Inline mode. AnswerInlineQuery, the InlineQuery and ChosenInlineResult update kinds, and the two result cards the family uses: InlineQueryResultPhoto and InlineQueryResultArticle with InputTextMessageContent. Answering with an empty result list is now expressible, and results is always sent, because an omitted parameter is a 400 rather than "nothing found".
• LinkPreviewOptions as a type, SendTextWithPreview for the one case where a bot relays text whose author wanted the preview, and AnswerCallbackQueryURL for a button that opens a t.me deep link with no intermediate message.

... (truncated)

Commits

• e591a70 merge: v0.1.0
• bb6fbad release: cut the stable version
• 2c84472 release: prepare v0.1.0-alpha.2
• 16a12d6 docs: write down how this stack is actually deployed
• 55b79db release: v0.1.0-alpha.1
• 2225ab1 Suppress the link preview on an ephemeral text edit
• 262c8f9 Add media sends and inline mode
• 5c9f50c docs: one versioning and release contract for the whole family
• 0c2fb37 feat(release): publish a GitHub Release for each tag
• cd06c73 ci: pin every action to a commit, one version across the family
• Additional commits viewable in compare view

Updates github.com/jackc/pgx/v5 from 5.9.2 to 5.11.0

Release notes

Sourced from github.com/jackc/pgx/v5's releases.

v5.11.0

This release adds direct PostgreSQL type scanning through database/sql on Go 1.27, improves compatibility with libpq connection strings and PostgreSQL date/time values, and includes further decoder hardening. See Changes for connection-string and date/time behavior changes that may affect existing applications.

Features

• stdlib: support Go 1.27's driver.RowsColumnScanner, allowing PostgreSQL types such as arrays and ranges to be scanned directly into Go values without pgtype.Map.SQLScanner. Existing database/sql scalar conversions and sql.Scanner behavior are preserved. The minimum supported Go version remains 1.25.
• Add Rows.TypeMap to expose the type map used to decode rows, including rows created by RowsFromResultReader that have no underlying Conn. Custom implementations of Rows, including mocks, must add this method.
• pgconn: add Config.MaxProtocolMessageBodyLen to configure the maximum incoming protocol message body size (carter-ya)
• pgconn: add ErrReadOnlyConnection, ErrReadWriteConnection, ErrPrimaryConnection, and ErrStandbyConnection sentinel errors for target_session_attrs validation, allowing callers to use errors.Is (Adrian-Stefan Mares)
• pgxpool: accept pool_ping_timeout in connection strings to configure Config.PingTimeout. The default is zero; zero and negative durations mean no timeout (1991santhu)

Changes

• Name-based row-to-struct mapping now matches explicit db tags case-insensitively, with exact matches taking precedence so tags can still distinguish quoted column names that differ only by case (AlisinaDevelo)

• pgconn: resolve the OS user account only when no user is supplied by the connection string, environment, or service file, avoiding unnecessary account lookups and crashes in some restricted container environments. Home-directory defaults for password, service, and TLS files remain available independently of the account lookup. On Unix these now use $HOME rather than the OS account's home directory (Mohamed MAACHE)

• pgtype: date, timestamp and timestamptz text values are now parsed and written by a hand-written parser and encoder for PostgreSQL's ISO date/time format instead of time.Parse and time.Format. Go's layout language cannot express a variable-width year or the BC era, which is the root of the bugs below. The text scan path is roughly 2.5x faster for timestamp and timestamptz. Bug fixes:

  • timestamp and timestamptz no longer silently move February 29 of a BC leap year to March 1 when encoding. time.Date(-4712, 2, 29, ...) was written as 4713-03-01 BC and is now written as 4713-02-29 BC. This affected ordinary four-digit BC years, not only extended-range ones. date was never affected.
  • timestamp and timestamptz can now scan BC leap days. 4713-02-29 BC previously failed with day out of range. date could already scan them.
  • Years past 9999 can now be scanned. 10000-01-02 03:04:05 previously failed to parse, so timestamp and timestamptz values at the high end of PostgreSQL's range were unreadable over the simple protocol and in any other text-format result.
  • time.Time arguments in the simple protocol now encode BC dates correctly, using the same timestamp encoder.
  • Fractional seconds beyond microsecond precision are rounded the way the server rounds them (round half to even, carrying into the rest of the value) instead of being kept at full precision. PostgreSQL never sends more than six fractional digits, so this only affects values from other sources.

  Behavior changes:

  • date now rejects impossible dates instead of normalizing them. 2024-02-30 returned 2024-03-01 and 2024-13-01 returned 2025-01-01; both are now errors. timestamp and timestamptz already rejected them.
  • All three types now reject values outside PostgreSQL's range for that type, in the binary format as well as the text format. PostgreSQL never sends out-of-range dates, so this only affects corrupt or hand-built input; the range

... (truncated)

Changelog

Sourced from github.com/jackc/pgx/v5's changelog.

5.11.0 (September 7, 2026)

This release adds direct PostgreSQL type scanning through database/sql on Go 1.27, improves compatibility with libpq connection strings and PostgreSQL date/time values, and includes further decoder hardening. See Changes for connection-string and date/time behavior changes that may affect existing applications.

Features

• stdlib: support Go 1.27's driver.RowsColumnScanner, allowing PostgreSQL types such as arrays and ranges to be scanned directly into Go values without pgtype.Map.SQLScanner. Existing database/sql scalar conversions and sql.Scanner behavior are preserved. The minimum supported Go version remains 1.25.
• Add Rows.TypeMap to expose the type map used to decode rows, including rows created by RowsFromResultReader that have no underlying Conn. Custom implementations of Rows, including mocks, must add this method.
• pgconn: add Config.MaxProtocolMessageBodyLen to configure the maximum incoming protocol message body size (carter-ya)
• pgconn: add ErrReadOnlyConnection, ErrReadWriteConnection, ErrPrimaryConnection, and ErrStandbyConnection sentinel errors for target_session_attrs validation, allowing callers to use errors.Is (Adrian-Stefan Mares)
• pgxpool: accept pool_ping_timeout in connection strings to configure Config.PingTimeout. The default is zero; zero and negative durations mean no timeout (1991santhu)

Changes

• Name-based row-to-struct mapping now matches explicit db tags case-insensitively, with exact matches taking precedence so tags can still distinguish quoted column names that differ only by case (AlisinaDevelo)

• pgconn: resolve the OS user account only when no user is supplied by the connection string, environment, or service file, avoiding unnecessary account lookups and crashes in some restricted container environments. Home-directory defaults for password, service, and TLS files remain available independently of the account lookup. On Unix these now use $HOME rather than the OS account's home directory (Mohamed MAACHE)

• pgtype: date, timestamp and timestamptz text values are now parsed and written by a hand-written parser and encoder for PostgreSQL's ISO date/time format instead of time.Parse and time.Format. Go's layout language cannot express a variable-width year or the BC era, which is the root of the bugs below. The text scan path is roughly 2.5x faster for timestamp and timestamptz. Bug fixes:

  • timestamp and timestamptz no longer silently move February 29 of a BC leap year to March 1 when encoding. time.Date(-4712, 2, 29, ...) was written as 4713-03-01 BC and is now written as 4713-02-29 BC. This affected ordinary four-digit BC years, not only extended-range ones. date was never affected.
  • timestamp and timestamptz can now scan BC leap days. 4713-02-29 BC previously failed with day out of range. date could already scan them.
  • Years past 9999 can now be scanned. 10000-01-02 03:04:05 previously failed to parse, so timestamp and timestamptz values at the high end of PostgreSQL's range were unreadable over the simple protocol and in any other text-format result.
  • time.Time arguments in the simple protocol now encode BC dates correctly, using the same timestamp encoder.
  • Fractional seconds beyond microsecond precision are rounded the way the server rounds them (round half to even, carrying into the rest of the value) instead of being kept at full precision. PostgreSQL never sends more than six fractional digits, so this only affects values from other sources.

  Behavior changes:

  • date now rejects impossible dates instead of normalizing them. 2024-02-30 returned 2024-03-01 and 2024-13-01 returned 2025-01-01; both are now errors. timestamp and timestamptz already rejected them.
  • All three types now reject values outside PostgreSQL's range for that type, in the binary format as well as the

... (truncated)

Commits

• 5e583fa Update changelog for v5.11.0
• 3927116 Apply gofumpt formatting required by lint
• eb07165 Quote filesystem paths in development connection strings
• cf5938f Allow unsigned digit counts in binary numeric encoding
• 3930cf5 Accept PostgreSQL POSIX timezone offsets in text timestamps
• 93261be Prefer exact db tag matches when mapping rows to structs
• e8d8ad1 Merge pull request #2647 from sueun-dev/fix-range-text-quoting-20260906
• 01d2fd3 Merge pull request #2644 from eliranbz/fix-failed-prepare-deallocation
• 9b7e3be Merge pull request #2645 from ash2k/move-channel
• 76d78f5 Merge pull request #2643 from AshSgDe29071999/fix/hstore-pairs-estimate-clamp
• Additional commits viewable in compare view