build(deps): bump the dependencies group across 1 directory with 2 updates

[dependabot]

Bumps the dependencies group with 2 updates in the / directory: github.com/pressly/goose/v3 and github.com/sirupsen/logrus.

Updates github.com/pressly/goose/v3 from 3.27.3 to 3.28.0

Release notes

Sourced from github.com/pressly/goose/v3's releases.

v3.28.0

Added

• CLI: azuresql driver for Azure SQL with Microsoft Entra ID (Azure AD) authentication via fedauth connection string parameters, e.g. goose azuresql "sqlserver://host?database=mydb&fedauth=ActiveDirectoryDefault" status. Excluded when building with the no_mssql or no_azuresql tags (#1109)
• MySQL/MariaDB table-based Locker via lock.NewMySQLTableLocker, the MySQL counterpart to the Postgres table locker from #993, accepting the same TableLockerOption set (#1075)

Changed

• Minimum Go version is now 1.26
• ClickHouse: new goose_db_version tables are created with ORDER BY (version_id) instead of ORDER BY (date). Existing tables are unchanged (#1085)
• MySQL/TiDB: the tstamp column is now DATETIME instead of TIMESTAMP, which is capped at 2038-01-19 (#1053). Only newly created tables are affected; existing tables can be updated with:

  ALTER TABLE goose_db_version MODIFY tstamp datetime NULL DEFAULT CURRENT_TIMESTAMP;

• Various dependency upgrades

Fixed

• goose create returns a clear "file exists" error, including the path, instead of %!w(<nil>) when the migration file already exists (#1104)

Changelog

Sourced from github.com/pressly/goose/v3's changelog.

[v3.28.0] - 2026-09-02

Added

• CLI: azuresql driver for Azure SQL with Microsoft Entra ID (Azure AD) authentication via fedauth connection string parameters, e.g. goose azuresql "sqlserver://host?database=mydb&fedauth=ActiveDirectoryDefault" status. Excluded when building with the no_mssql or no_azuresql tags (#1109)
• MySQL/MariaDB table-based Locker via lock.NewMySQLTableLocker, the MySQL counterpart to the Postgres table locker from #993, accepting the same TableLockerOption set (#1075)

Changed

• Minimum Go version is now 1.26

• ClickHouse: new goose_db_version tables are created with ORDER BY (version_id) instead of ORDER BY (date). Existing tables are unchanged (#1085)

• MySQL/TiDB: the tstamp column is now DATETIME instead of TIMESTAMP, which is capped at 2038-01-19 (#1053). Only newly created tables are affected; existing tables can be updated with:

  ALTER TABLE goose_db_version MODIFY tstamp datetime NULL DEFAULT CURRENT_TIMESTAMP;

• Various dependency upgrades

Fixed

• goose create returns a clear "file exists" error, including the path, instead of %!w(<nil>) when the migration file already exists (#1104)

Commits

• 43d2d9c release: v3.28.0
• c65c559 docs: update changelog
• 674e150 fix: use DATETIME instead of TIMESTAMP for MySQL/TiDB tstamp column (Y2K38) (...
• f604e88 fix: include path in duplicate migration file error and use 0666 mode
• 5f12f79 fix: return clear error when migration file already exists (#1104)
• 4766566 fix: use version_id instead of date as ordering key (#1085)
• 751ff94 docs: add Go 1.26.0 bump and dependency upgrades to changelog
• 34124ac fix: wait for an alive StarRocks backend in tests (#1114)
• f5caf10 chore: bump dependencies and go to 1.26.0 (#1113)
• 2e8e87a Add azuresql driver with EntraID auth (#1109)
• Additional commits viewable in compare view

Updates github.com/sirupsen/logrus from 1.10.0 to 1.10.2

Release notes

Sourced from github.com/sirupsen/logrus's releases.

v1.10.2

Logrus v1.10.2

This is a small maintenance release that updates github.com/stretchr/testify to v1.12.1, removing the legacy gopkg.in/yaml.v3 dependency from Logrus' dependency graph. There are no functional changes in this release.

Dependency Changes

• update github.com/stretchr/testify to v1.12.1

Full Changelog: sirupsen/logrus@v1.10.1...v1.10.2

v1.10.1

Logrus v1.10.1

This patch release fixes two issues in field formatting and handling:

• Fix a regression introduced in v1.10.0 where TextFormatter could panic when formatting nil or panicking error and fmt.Stringer values.
• Allow function-backed values implementing error to be used with WithError, WithField, and WithFields.

Dependency Changes

• update github.com/stretchr/testify to v1.12.0

Full Changelog: sirupsen/logrus@v1.10.0...v1.10.1

Changelog

Sourced from github.com/sirupsen/logrus's changelog.

1.10.2

Changed:

• Update github.com/stretchr/testify to v1.12.1, removing the legacy gopkg.in/yaml.v3 dependency.

1.10.1

Fixes:

• Fix a regression introduced in v1.10.0 where TextFormatter could panic when formatting nil or panicking error and fmt.Stringer values.
• Allow function-backed implementations of error as field values.

Commits

• 6d6a132 Merge pull request #1586 from thaJeztah/prepare_v1.10.2
• 4f94653 update changelog for v1.10.2
• 87434bb Merge pull request #1585 from thaJeztah/bump_testify
• e7d2120 chore(deps): bump github.com/stretchr/testify v1.12.1
• 8b673a9 Merge pull request #1583 from thaJeztah/release_1.10.1
• 0b920ad Merge pull request #1584 from thaJeztah/more_coverage
• 5e20694 TextFormatter: cover nil pointer method receivers
• 8312732 update changelog for v1.10.1
• e987a40 Merge pull request #1582 from thaJeztah/panic_handler
• 17d574b TextFormatter: recover panics from Error and String methods
• Additional commits viewable 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

[redpandabot]

Summary

Dependabot group bump for goose v3.27.3→v3.28.0 and logrus v1.10.0→v1.10.2, with the associated transitive churn (modernc/sqlite, otel, x/net, x/crypto, etc.). The goose API used in daemon/db/database.go (SetDialect/Up/UpByOne/UpTo/WithAllowMissing) is unchanged in 3.28.0, so the upgrade itself is mechanical. Two items stand out: the newly-pinned golang.org/x/crypto v0.55.0 carries open OSV SSH advisories, and the go directive was raised to 1.26.0 while CI/Dockerfile/docs still pin Go 1.25.

Issues

• 🔴 go.mod:81 — golang.org/x/crypto v0.55.0 pinned with known SSH DoS advisories — see the thread on that line
• 🟡 go.mod:3 — go directive raised to 1.26.0 but toolchain pins/docs still say Go 1.25 — goose v3.28.0 requires Go 1.26, so the go.mod bump is correct, but the repo still pins go-version: 1.25.x (_shared-check.yaml:21, _shared-build.yaml, dependabot-fix.yml:30) and FROM golang:1.25 (Dockerfile:2), and CLAUDE.md/README/docs say "Go 1.25+". CI only stays green via GOTOOLCHAIN=auto downloading go1.26.0 on the fly; anything running 1.25 with GOTOOLCHAIN=local (which _shared-check.yaml's staticcheck comment explicitly accounts for) hard-fails on the build. Align the pins and docs with 1.26.

---

_{Reviewed @ f366833c
"If the user can't use it, it doesn't work." — Susan Dray}

[redpandabot]

🔴 golang.org/x/crypto v0.55.0 pinned with known SSH DoS advisories

OSV reports GO-2026-6354 (CVE-2026-78662) and GO-2026-6355 (CVE-2026-56855) for golang.org/x/crypto/ssh, fixed in v0.56.0; the version this PR pins (v0.55.0) is affected. It is transitive (spamoor code imports neither x/crypto nor x/crypto/ssh) and the predecessor v0.54.0 was equally affected (0.54→0.55 even fixes GO-2026-6303), so no new exposure vs master — but the resulting dependency tree should be bumped to v0.56.0 rather than merged with a known-vulnerable stdlib-adjacent package.