Skip to content

Bump Go to 1.26.10 and patch activesupport, rack, addressable - #235

Merged
jeremy merged 2 commits into
mainfrom
fix/security-advisories-2026-11
Nov 5, 2026
Merged

jeremy merged 2 commits into
mainfrom
fix/security-advisories-2026-11

Conversation

@jeremy

@jeremy jeremy commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

The security workflow is red on every PR (including #233 and #234) because of new advisories, not anything those PRs changed. This fixes them at the source.

  • Go Vulnerability Check: GO-2026-6809 (crypto/x509 in the go1.26.9 stdlib) is fixed in go1.26.10. Bump the go directive in go/go.mod, conformance/runner/go/go.mod and go.work; every workflow's setup-go reads go-version-file: go/go.mod, so CI picks it up with no workflow change.
  • Bundler Audit / Trivy (Ruby): ruby/Gemfile.lock moves activesupport 8.1.2.1 → 8.1.4.1, rack 3.2.6 → 3.2.8, addressable 2.9.0 → 2.9.2 (bundle update --conservative, nothing else moved; BUNDLED WITH left at 4.0.13).

Locally: govulncheck ./... (v1.1.4, go1.26.10) reports no vulnerabilities; bundle-audit check --update reports none; Go tests and the Ruby suite (117 runs) pass.

No spec or generated code changes; nothing here needs a release on its own.


Summary by cubic

Fixes the security workflow that was failing on every PR due to new advisories unrelated to those PRs.

Bumps the Go toolchain from 1.26.9 to 1.26.10 across go.work, go/go.mod, and conformance/runner/go/go.mod to fix GO-2026-6809 (crypto/x509). CI picks this up automatically since setup-go reads go-version-file: go/go.mod.

Applies a conservative bundle update in ruby/Gemfile.lock, patching activesupport 8.1.2.1 → 8.1.4.1, rack 3.2.6 → 3.2.8, and addressable 2.9.0 → 2.9.2. Regenerated the lockfile with the locked Bundler (4.0.13), which a hand-edited BUNDLED WITH had left inconsistent and failing frozen installs on CI. govulncheck and bundle-audit report no vulnerabilities, and both test suites pass.

Written for commit 4509a29. Summary will update on new commits.

View guided diff Turn on auto-fix

govulncheck flags GO-2026-6809 in crypto/x509, fixed in go1.26.10; CI
reads the toolchain from go/go.mod. Bundler Audit and Trivy flag
activesupport 8.1.2.1, rack 3.2.6 and addressable 2.9.0; move each to the
first patched release (8.1.4.1, 3.2.8, 2.9.2).
Copilot AI balanced review requested due to automatic review settings November 5, 2026 23:19
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 5, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-05T23:38:09.941791Z 4509a29 Manual request
🔒 Security Review ✅ Completed 2026-11-05T23:39:26.884353Z 4509a29 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

View guided diff | Turn on auto-fix | Re-trigger cubic

The hand-restored BUNDLED WITH left the lockfile inconsistent, and
frozen bundle install on CI refused it.
Copilot AI previously approved these changes Nov 5, 2026

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approved

No active review issues are identified for the dependency and Go version updates.

No open issues 🎉

What changed in this PR

Updates Go and Ruby dependencies to address security advisories causing shared CI failures, including those affecting #233 and #234. No SDK behavior, spec, or generated code changes are included.

Changes:

  • Raises Go from 1.26.9 to 1.26.10 across both modules and the workspace.
  • Patches activesupport, rack, and addressable, with updated checksums.
  • Updates the lockfile’s Bundler version from 4.0.13 to 4.0.20.

[!TIP]
If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.

File Description
ruby/​Gemfile.lock Updates three gems, their checksums, and the Bundler version.
go/​go.mod Raises the SDK’s minimum Go version to 1.26.10.
go.work Aligns the workspace with Go 1.26.10.
conformance/​runner/​go/​go.mod Aligns the conformance runner with Go 1.26.10.

Review effort: Balanced

@chatgpt-codex-connector

Copy link
Copy Markdown

💡 Codex Review


P2 Badge Synchronize the selected Bundler and its checksum

The Ruby CI matrix explicitly selects Bundler from this lockfile footer (.github/workflows/test.yml:98-103), so it will install 4.0.20, while the CHECKSUMS section still records only bundler (4.0.13) at line 166. This leaves the security metadata authenticating a different artifact from the one CI uses and causes a subsequent Bundler 4 lock refresh to rewrite the lockfile; either retain 4.0.13 here as intended or update its checksum to the 4.0.20 checksum.

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@jeremy

jeremy commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

Fixed — 4509a29 regenerates the lockfile with Bundler 4.0.13, the version main locks: BUNDLED WITH and the bundler (4.0.13) checksum agree again, and the diff against main is only the three gem bumps. That mismatch was also why Bundler Audit's frozen install failed on fe8d3f9.

@jeremy
jeremy requested a balanced review from Copilot November 5, 2026 23:36
@jeremy

jeremy commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

@codex review

Copilot AI dismissed their stale review, a newer Copilot review was requested November 5, 2026 23:37
@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. You're on a roll.

Reviewed commit: 4509a29731

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approved

No active review issues were identified for the dependency and Go version updates.

No open issues 🎉

Review effort: Balanced

@chatgpt-codex-connector

Copy link
Copy Markdown

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 4509a29731

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@jeremy

jeremy commented Nov 5, 2026

Copy link
Copy Markdown
Member Author

Review bodies: 1 finding answered (1 fixed).
Fixed from a review body:

@jeremy
jeremy merged commit 0950055 into main Nov 5, 2026
47 checks passed
@jeremy
jeremy deleted the fix/security-advisories-2026-11 branch November 5, 2026 23:44
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.

2 participants