Repository navigation
🌱 build(deps): update github.com/charmbracelet/x/ansi to 0.11.9 in /src - #16188
hivecommons-hive[bot] merged 14 commits into
Conversation
Bumps [github.com/charmbracelet/x/ansi](https://github.com/charmbracelet/x) from 0.10.1 to 0.11.9. - [Commits](charmbracelet/x@ansi/v0.10.1...ansi/v0.11.9) --- updated-dependencies: - dependency-name: github.com/charmbracelet/x/ansi dependency-version: 0.11.9 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Open PR overlap checkBase branch: Conflicts are checked with every PR merged onto the current tip of
|
e5d300a
ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blockedHive flagged this PR (author @dependabot[bot], head
Hive did not add the |
Regenerated by .github/workflows/notice-autofix.yml from the module graph in this branch's src/go.mod and src/go.sum. See #5256. Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
hive-ci-triage:
This bump cannot land on its own: it needs a coordinated bubbletea/lipgloss/cellbuf upgrade. Recommendation: The 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
There was a problem hiding this comment.
This bump cannot land as-is: it breaks the build of a transitive dependency, and the red build / build-and-test / test (rest …) checks are this diff's fault, not infrastructure.
Mechanism. src/go.mod:8 moves github.com/charmbracelet/x/ansi to v0.11.9 but leaves github.com/charmbracelet/x/cellbuf v0.0.13-0.20250311204145-2c3ea96c31dd // indirect (src/go.mod:39) untouched. ansi 0.11 changed the ansi.Style API (attribute methods now take arguments; SlowBlink, DoubleUnderline, CurlyUnderline, DottedUnderline removed/renamed), and that cellbuf snapshot still calls the 0.10 shape. From the build-and-test log (job 125071203599):
cellbuf@v0.0.13-0.20250311204145-2c3ea96c31dd/cell.go:195:8: not enough arguments in call to b.Italic
cellbuf@v0.0.13-0.20250311204145-2c3ea96c31dd/cell.go:198:10: b.SlowBlink undefined (type ansi.Style has no field or method SlowBlink)
cellbuf@v0.0.13-0.20250311204145-2c3ea96c31dd/cell.go:218:10: b.DoubleUnderline undefined …
cellbuf is reached via pkg/tui → github.com/charmbracelet/lipgloss v1.1.0 → cellbuf (go mod why -m at the PR head), so every binary that links the TUI fails to compile.
What would make it mergeable. Either bump x/cellbuf together with x/ansi to a pair that compiles against each other (and re-run go mod tidy + the NOTICE regeneration already in this PR), or hold x/ansi at 0.10.x until lipgloss/bubbletea move to a cellbuf that targets ansi 0.11. Dependabot will not do the coupled bump on its own; it needs a human (or a grouped update rule for github.com/charmbracelet/*) so these move in lockstep.
Recommend not merging this one. I have not closed anything.
— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor. Review findings from Looks correct to me; the two red checks are not caused by this diff.
Flagging for a maintainer: re-run |
…ompatibility cellbuf v0.0.13-0.20250311204145 calls ansi.Style methods (Italic, SlowBlink, DoubleUnderline, ...) whose signatures changed in ansi v0.11, breaking go build. Bump the indirect cellbuf dependency to v0.0.15 (pulls colorprofile v0.4.1) and regenerate NOTICE for the new versions. Hive-Fix-Attempt: 1/6 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Signed-off-by: ci-maintainer <280983584+hivecommons-hive[bot]@users.noreply.github.com>
…elet/x/ansi-0.11.9
…elet/x/ansi-0.11.9
|
hive-ci-triage update: the build/lint/test failures noted above have since gone green on head 7fecd5b ( 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
|
CI triage — Job 125085828097 on head 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
|
Owner-requested, agent-assisted decision under @clubanderson's explicit delegation for this batch; this is not a separate independent human review. Reviewed the current diff and surrounding source at the exact commit below. Exact current head |
|
Additional exact-check evidence, without consuming REST run-log quota: the failed current-head gosec CheckRun annotation reads “The self-hosted runner lost communication with the server.” This establishes runner loss, not an asserted OOM or source vulnerability. The required check remains failed and may not be bypassed. Existing dependency/shared-CI owner: inspect the actual Scan job log after normal quota reset and use the established incident/repair path; the compatible cellbuf bump is already present and should not be reimplemented. The title repair is now present but the old PR Type check must also be refreshed through its normal provider. |
|
@dependabot rebase 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
|
Sorry, only users with push access can use that command. |
…elet/x/ansi-0.11.9
There was a problem hiding this comment.
The one red check here is stale, not a defect in the bump.
Why PR Type is red: check-run 125611179880 ran at 2026-11-02T02:56Z against the original Dependabot title build(deps): bump github.com/charmbracelet/x/ansi from 0.10.1 to 0.11.9 in /src and reported "No matching PR type indicator found in title". The title has since been corrected to 🌱 build(deps): … (PR updated 23:24Z), but no new pull_request run of the PR-Type check exists on head 5efdc5f — the title edit did not retrigger it. A maintainer re-running the failed Dashboard Lint run (or Dependabot @dependabot recreate) should clear it; nothing in the diff needs to change.
The change itself (read at 5efdc5f):
src/go.mod: direct bumpcharmbracelet/x/ansi0.10.1 → 0.11.9 plus the transitive bumps it drags in (colorprofile0.4.1,cellbuf0.0.15,go-colorful1.4.1,go-runewidth0.0.27) and two new indirect deps (clipperhouse/displaywidth0.11.0,clipperhouse/uax29/v22.7.0).NOTICEis updated to match — both new clipperhouse packages (MIT) and all bumped versions/sources are present, so the license inventory stays in sync withgo.mod.v2 CI,v2 Tests(test / coverage / patch-coverage), Go Security Analysis and FOSSA are all green on this head.
Looks correct to me; only the stale check stands between this and the queue.
— reviewer agent
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
hive-ci-triage correction: 🐝 Hive Agent: — hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
…elet/x/ansi-0.11.9
|
🐝 Hive Agent: — hive: agent=quality backend=copilot model=claude-fable-5.1 copilot=1.0.88 |
There was a problem hiding this comment.
The red checks here are not this bump. test (rest 2/4) fails in pkg/writeback TestDirectWriteRatchet (ratchet_test.go:179): automerge_stage_labels.go: 5 direct write call(s), baseline 3 and pr_status_comment.go: 2 direct write call(s) in a file not in the baseline. Those files are untouched by this PR; the ratchet broke on v5 itself when #16319/#16321 moved the status-comment edit/create/delete into prstatus.Forge adapters without annotating them. A fix for that is currently riding inside #16300 (commit 33a09b7); once it lands on v5 and this PR re-runs, the bump itself — go.mod/go.sum/go.work.sum/NOTICE only — looks correct to me.
— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
The hive's GitHub App lacks |
|
Needs a decision, not a merge: Clear the cause and the hive re-evaluates on its next pass; the stage moves to |
|
Owner-authorized decision following clubanderson request: HOLD the shared-CI rerun; no rerun or approval at current head 1e54c9e. Fresh v5 protection requires Alternative: carry the existing baseline repair through the normal author/head-refresh path, then inspect required CI on the new exact head; only a separately justified transient failed job merits one bounded maintainer rerun. The current PR Type failure also quotes the old unprefixed title although the title is now prefixed; do not spoof its success. The authenticated GitHub account clubanderson has maintainer/admin rights, but Hive's App denial remains real and is not overridden. No issue fabricated, old-head review reused, reviewer dispatch, policy/label change or merge authorized. This records the decision; it does not claim the native unauthorized hold is cleared. |
…elet/x/ansi-0.11.9
…elet/x/ansi-0.11.9
There was a problem hiding this comment.
Looks correct to me; the only thing holding this is a stale check, not the change.
- The red
PR Typecheck evaluated the old title. Its output says: "I saw a title ofbuild(deps): bump github.com/charmbracelet/x/ansi from 0.10.1 to 0.11.9 in /src". The PR has since been retitled with the🌱prefix, which that check accepts, but the retitle did not re-run it. A maintainer re-running thePR Typecheck (or any new push) should clear it; nothing in the diff needs to change. - Code impact is minimal. The only direct consumer of this module is
src/pkg/tui/panes/hives_tree.go:806,840,852(ansi.Hardwrap,ansi.Truncate);build-go,golangci-lintand alltest (…)shards are green on4502e72, so the 0.10→0.11 API is compatible with those call sites. NOTICEis regenerated for the four new/updated transitive modules (colorprofile 0.4.1, cellbuf 0.0.15, clipperhouse/displaywidth 0.11.0, clipperhouse/uax29 2.7.0, go-colorful 1.4.1, go-runewidth 0.0.27 — all MIT) and the "NOTICE matches the module graph" check passes;govulncheckis green.
I have not changed anything on this PR.
— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88
…elet/x/ansi-0.11.9
There was a problem hiding this comment.
The only red check here is stale, not a defect. PR Type (run 125693621886) evaluated the original title build(deps): bump github.com/charmbracelet/x/ansi from 0.10.1 to 0.11.9 in /src and has not re-run since the PR was retitled with the 🌱 prefix it asks for; a re-run of that check (or any title edit) should turn it green.
The change itself is a routine minor bump: src/go.mod moves charmbracelet/x/ansi 0.10.1 → 0.11.9 as the one direct dependency, with colorprofile, cellbuf, go-runewidth and two new clipperhouse indirects pulled along; NOTICE is updated to match and the "NOTICE matches the module graph" check, govulncheck, and every test shard pass at 4502e72. Looks fine to me.
— hive: agent=reviewer backend=copilot model=claude-fable-5.1 copilot=1.0.88
01fd511
ℹ️ Sentinel notice — informational; author is trusted (allow-listed bot), merge is not blockedHive flagged this PR (author @dependabot[bot], head
Hive did not add the |
…elet/x/ansi-0.11.9
There was a problem hiding this comment.
Looks correct to me; the one red check is stale, not a defect.
github.com/charmbracelet/x/ansi0.10.1 → 0.11.9 with transitive bumps (cellbuf,colorprofile,go-runewidth, newclipperhouse/displaywidth,uax29). The repo's only direct uses areansi.Hardwrapandansi.Truncateinsrc/pkg/tui/panes/hives_tree.go:806,840,852; both signatures are unchanged in 0.11.x andbuild-go,golangci-lint, and everytest (…)shard pass atafcb8c9.PR Typeis failing on the previous title. The check output says: "I saw a title ofbuild(deps): bump github.com/charmbracelet/x/ansi from 0.10.1 to 0.11.9 in /src", but the PR is now titled🌱 build(deps): update …. The check did not re-run after the retitle; a no-op title edit (or re-running thePR Typejob) should clear it. Nothing in the diff needs to change.
— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88
…elet/x/ansi-0.11.9
There was a problem hiding this comment.
Both red checks on 9b0ddfb are not caused by this diff; the bump itself is clean.
PR Typefailed at 02:56Z against the original titlebuild(deps): bump …("No matching PR type indicator found in title"). The title was retitled to🌱 build(deps): …at 03:07Z and again at 18:17Z, but the check never re-ran on the same head, so it is reporting a title that no longer exists. A re-run (or any new push) clears it.build-hub (linux/arm64, …)failed in buildx resolvingmirror.gcr.io/library/alpine:3.24@sha256:294b683…("failed to resolve source metadata") — registry-mirror infrastructure, nothing in the four changed files (NOTICE,src/go.mod,src/go.sum,src/go.work.sum). The amd64 hub build and every Go test shard on this head are green, soansi0.11.9 (with transitivecolorprofile0.4.1 /cellbuf0.0.15) compiles and passes against the tree.
NOTICE is regenerated consistently with the new transitive versions (NOTICE matches the module graph is green). Looks correct to me; only the two stale/infra checks stand between this and the queue.
— hive: agent=reviewer-2 backend=copilot model=claude-fable-5.1 copilot=1.0.88
|
Thank you for your contribution! Your PR has been merged. We'd love to hear how your experience was: share feedback |
Bumps github.com/charmbracelet/x/ansi from 0.10.1 to 0.11.9.
Commits
faa4adfansi/v0.11.909f7503feat(ansi): OSC 7501 (#1004)ad85c59chore(powernap): update lsp configs from nvim-lspconfig953920dnerdfont/v0.1.04edfc00feat(nerdfont): overrides (#1000)7be62f4chore(deps): bump golang.org/x/sys in /term in the all group (#996)29bfdbdfeat: nerdfont9c77d67chore(powernap): update lsp configs from nvim-lspconfigd676b01v0.1.0 for charmtone and slices53e2afechore(powernap): update lsp configs from nvim-lspconfigDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)