Skip to content

Merge branch 'v2.4.x' into develop#5005

Open
kaidaguerre wants to merge 14 commits into
developfrom
merge-v2.4.x-into-develop
Open

Merge branch 'v2.4.x' into develop#5005
kaidaguerre wants to merge 14 commits into
developfrom
merge-v2.4.x-into-develop

Conversation

@kaidaguerre
Copy link
Copy Markdown
Contributor

Brings v2.4.x release line (v2.4.1 through v2.4.4 + workflow fix cherry-pick #5004) forward to develop. Closes Vanta SLA finding for pgx CVE-2026-41889 on default branch.

Conflicts resolved

  • go.mod / go.sum: took v2.4.x's dep versions (pgx v5.9.2, pipe-fittings v2.9.1, go-jose/v4 v4.1.4, otel v1.43.0, go-billy v5.8.0). Ran go mod tidy to preserve develop's SDK v6 imports (steampipe-plugin-sdk/v6 v6.0.0 — develop is on v6, v2.4.x is on v5; tidy regenerated the SDK pin based on develop's source imports).
  • Other files: auto-merged.

Verification

  • go build ./... — pass
  • go vet ./... — 3 pre-existing warnings (unrelated to merge)

graza-io and others added 14 commits March 10, 2026 15:06
Bump grpc to v1.79.3 (CVE-2026-33186), otel/sdk to v1.40.0
(CVE-2026-24051), and swap pgconn v1 import to pgx/v5/pgconn to
remove pgproto3/v2 (CVE-2026-4427). Closes #4963

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ns (#4965) (#4975)

(cherry picked from commit 0722f84)

Co-authored-by: cbruno10 <cody@turbot.com>
…4982)

pipe-fittings v2.9.1 adds an anonymous retry to OCI pulls when stored
GHCR credentials (from ~/.docker/config.json) are rejected. Without
this, an expired or revoked PAT causes 'steampipe plugin install' to
fail with an opaque 403 even when the image is publicly pullable.

Also updates cloud.bats acceptance test fixtures (AWS account
632902152528 / alias 'nagraj-aaa' → 097350876455 / 'turbot-silverwater')
to match the current turbot-ops/clitesting workspace state.
Raise the direct dependency github.com/jackc/pgx/v5 from v5.7.6 to
v5.9.2 to remediate CVE-2026-41889, plus go mod tidy. Dependency-only:
no Go toolchain bump (go.mod already declares go 1.26.1) and no
behavioral code changes (pgx v5.7.6 -> v5.9.2 behavioral analysis found
0 affected sites in steampipe). go build ./... and go test ./... pass.

Refs #4989
- go-jose/go-jose/v4 v4.1.3 -> v4.1.4 (CVE-2026-34986)
- go.opentelemetry.io/otel/sdk v1.40.0 -> v1.43.0 (CVE-2026-24051, CVE-2026-39883)
- Add v2.4.3 CHANGELOG entry covering these plus the already-merged
  pgx/v5 v5.9.2 bump (CVE-2026-41889, #4990) on the v2.4.x line
The homebrew PR is created with title 'Steampipe <version>' (no v prefix,
using github.event.inputs.version via env.Version). The later check
compared against 'Steampipe v<version>' (using env.VERSION which prepends
a v). Mismatch caused update_homebrew_tap to always fail after tagging,
which then skipped trigger_smoke_tests.

Fix: check against github.event.inputs.version to match the PR title
convention used across historical homebrew-tap PRs (Steampipe 2.3.5,
2.3.6, 2.4.0, 2.4.1).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants