[deps] Update github.com/charmbracelet/x/exp/golden pseudoversion (Dec 2025 → Apr 2026)

[github-actions]

Summary

Update github.com/charmbracelet/x/exp/golden dependency from pseudoversion v0.0.0-20251215102626-e0db08df7383 (Dec 15, 2025) to v0.0.0-20260413095116-b18aac29f444 (Apr 13, 2026).

Current State

• Package: github.com/charmbracelet/x/exp/golden
• Current Version: v0.0.0-20251215102626-e0db08df7383 (Dec 15, 2025)
• Proposed Version: v0.0.0-20260413095116-b18aac29f444 (Apr 13, 2026)
• Update Type: Pseudoversion update (4-month gap, multiple commits)

Why Separate Issue

⚠️ Pseudoversion update with uncertain scope of changes

• This is an experimental package (exp/) using pseudoversioning (no semantic versions)
• The update spans approximately 4 months of commits (Dec 2025 → Apr 2026)
• Multiple intermediate commits may include functional changes to golden file testing
• Cannot determine the exact nature of all changes without reviewing the full commit history
• Used in test infrastructure — behavior changes could affect test golden files

Safety Assessment

⚠️ Requires careful review

• Experimental package with no stable versioned releases
• Pseudoversion spans a significant time period (4 months)
• The latest commit (b18aac29f444) is a dependabot bump in a sibling subpackage (unrelated to exp/golden)
• However, intermediate commits between Dec 2025 and Apr 2026 may have modified the exp/golden package
• Review git log for changes specifically in the exp/golden/ directory of the charmbracelet/x monorepo

Changes

• Repository: github.com/charmbracelet/x (monorepo)
• The exp/golden package provides golden file test utilities
• Recent commits in the repo are primarily dependabot bumps, but earlier commits may have changes to exp/golden
• Verify the golden test files in the codebase still work as expected after update

Links

• Package Repository
• exp/golden Source
• Commits since Dec 2025
• Go Package

Recommended Action

go get -u github.com/charmbracelet/x/exp/golden@v0.0.0-20260413095116-b18aac29f444
go mod tidy

Then review any golden file test changes:

go test ./... -update  # If the package supports golden file updating

Testing Notes

• Run all tests: make test
• Verify golden file tests still pass (tests in pkg/ that use golden file comparison)
• Check if any golden files need to be regenerated
• Review the exp/golden package API for any changes

Warning

⚠️ Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• go.googlesource.com

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "go.googlesource.com"

See Network Configuration for more information.

Note

🔒 Integrity filter blocked 20 items

The following items were blocked because they don't meet the GitHub integrity level.

• golang/mod@03901d3 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/mod@1ac721d list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/mod@fb1fac8 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/mod@27761a2 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/mod@4c04067 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/term@52b71d3 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/term@9d2dc07 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/term@d954e03 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/term@3aff304 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/term@a7e5b04 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@03ca0dc list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@8400f4a list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@81c6cb3 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@982eaa6 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@159944f list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• golang/crypto@a408498 list_commits: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 4 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

Generated by Dependabot Dependency Checker · ● 1.1M · ◷

• expires on Apr 15, 2026, 10:08 AM UTC

[github-actions]

🍪 Issue Monster has assigned this to Copilot!

I've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.

The Copilot coding agent will analyze the issue and create a pull request with the fix.

Om nom nom! 🍪

🍪 Om nom nom by Issue Monster · ● 232.5K · ◷