Skip to content

chore(deps): bump extractions/setup-just from 3 to 4#13

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/extractions/setup-just-4
Open

chore(deps): bump extractions/setup-just from 3 to 4#13
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/github_actions/extractions/setup-just-4

Conversation

@dependabot
Copy link
Copy Markdown

@dependabot dependabot bot commented on behalf of github Apr 12, 2026

Bumps extractions/setup-just from 3 to 4.

Commits

Dependabot compatibility score

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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [extractions/setup-just](https://github.com/extractions/setup-just) from 3 to 4.
- [Release notes](https://github.com/extractions/setup-just/releases)
- [Commits](extractions/setup-just@v3...v4)

---
updated-dependencies:
- dependency-name: extractions/setup-just
  dependency-version: '4'
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Apr 12, 2026
tony added a commit that referenced this pull request Apr 15, 2026
why: ``SparseArray`` lives at ``libtmux._internal.sparse_array`` —
     the ``_internal`` namespace is by libtmux convention a private
     module, so an upstream rename or move could break this import
     on a libtmux minor-version bump. That would take the whole
     MCP server down at import time, for a value that
     ``_flatten_hook_value`` already handles uniformly via
     ``hasattr(value, "items")``.

     Loom review Suggestion #13: wrap the import in a try/except so
     an upstream rename degrades to "treat values as dict" rather
     than crashing the server.

what:
- Replace the unguarded ``from libtmux._internal.sparse_array import
  SparseArray`` in src/libtmux_mcp/tools/hook_tools.py with a
  ``try/except ImportError`` block.
- Fallback defines a no-op ``SparseArray`` class that no runtime
  value will ever ``isinstance``-match — so the downstream
  ``hasattr(value, "items")`` branch in ``_flatten_hook_value``
  picks up both real ``SparseArray`` (when available) and plain
  ``dict`` (always available) shapes.
- Inline rationale documents the contract and pins it to libtmux
  0.55.x with a re-check note for 0.56+.
- ``# pragma: no cover`` on the ``except`` branch: the fallback only
  fires when libtmux's private module moves, which isn't reachable
  without a manual breakage.
- No test changes: the fallback contract is "never observable at
  runtime under supported libtmux versions". A test that forces the
  fallback would require fragile sys.modules manipulation; existing
  hook tests cover the import-succeeded path.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants