[dependabot]

Bumps the patch group with 2 updates in the / directory: open and similar.

Updates open from 5.4.4 to 5.4.5

Release notes

Sourced from open's releases.

v5.4.5

Bug Fixes

• check that_detached launchers for immediate failures that_detached() returned as soon as a launcher spawned, so a launcher that failed right after starting was reported as success and no fallback ran.

  Observe each launcher for 250 ms by delegating to that_detached_with_timeout(). A launcher that exits unsuccessfully within that window falls through to the next candidate; one still running is treated as handed off. The macOS and shellexecute-on-windows paths are unchanged.

  Extend the fixture tests to call that_detached() directly.

• restore launcher fallback and support Plasma 6

  When xdg-open starts but exits unsuccessfully, that() and the CLI previously stopped before trying another installed opener. On Plasma 6, the fallback list also omitted the versioned KDE launchers.

  Launcher behavior

  • Retry reported failures from UNIX desktop launchers and retain the first unsuccessful exit when later candidates are missing.
  • Add kde-open6 and kde-open5 before the existing kde-open fallback.
  • Keep launcher ordering, argument boundaries, and exit-status policy together so compatibility decisions are explicit.
  • Preserve Windows' stop-on-failure policy and the existing protections for option-shaped and non-UTF-8 paths.

  Bounded detached checks

  Add that_detached_with_timeout(path, timeout) to opt into checking the actual launcher status for a configurable interval per candidate. Retry confirmed UNIX launcher failures; consider successful exits or launchers still running at the deadline handed off. A zero timeout polls once.

  On UNIX, use setsid() while retaining the launcher as a child. Reserve a background waiter before spawning and transfer ownership after a timeout so the launcher can outlive its caller and is eventually reaped. Stop fallback if observing an already-started launcher fails, avoiding a second launch based only on a wait error. Existing detached calls retain their timing behavior. The new API uses command-based launchers on Windows, including when shellexecute-on-windows is enabled.

  Historical constraints

  55dc10d relaxed exit checks for argumentless availability probes, where usage errors are expected. It did not establish that failed real opening operations should stop fallback. 245c95e introduced that behavior; the earlier implementation retried unsuccessful operations.

... (truncated)

Changelog

Sourced from open's changelog.

5.4.5 (2026-10-22)

Bug Fixes

• check that_detached launchers for immediate failures that_detached() returned as soon as a launcher spawned, so a launcher that failed right after starting was reported as success and no fallback ran.

  Observe each launcher for 250 ms by delegating to that_detached_with_timeout(). A launcher that exits unsuccessfully within that window falls through to the next candidate; one still running is treated as handed off. The macOS and shellexecute-on-windows paths are unchanged.

  Extend the fixture tests to call that_detached() directly.

• restore launcher fallback and support Plasma 6

  When xdg-open starts but exits unsuccessfully, that() and the CLI previously stopped before trying another installed opener. On Plasma 6, the fallback list also omitted the versioned KDE launchers.

  Launcher behavior

  • Retry reported failures from UNIX desktop launchers and retain the first unsuccessful exit when later candidates are missing.
  • Add kde-open6 and kde-open5 before the existing kde-open fallback.
  • Keep launcher ordering, argument boundaries, and exit-status policy together so compatibility decisions are explicit.
  • Preserve Windows' stop-on-failure policy and the existing protections for option-shaped and non-UTF-8 paths.

  Bounded detached checks

  Add that_detached_with_timeout(path, timeout) to opt into checking the actual launcher status for a configurable interval per candidate. Retry confirmed UNIX launcher failures; consider successful exits or launchers still running at the deadline handed off. A zero timeout polls once.

  On UNIX, use setsid() while retaining the launcher as a child. Reserve a background waiter before spawning and transfer ownership after a timeout so the launcher can outlive its caller and is eventually reaped. Stop fallback if observing an already-started launcher fails, avoiding a second launch based only on a wait error. Existing detached calls retain their timing behavior. The new API uses command-based launchers on Windows, including when shellexecute-on-windows is enabled.

  Historical constraints

  55dc10d relaxed exit checks for argumentless availability probes, where usage errors are expected. It did not establish that failed real opening operations should stop fallback. 245c95e introduced that behavior;

... (truncated)

Commits

• a60a9d5 Release open v5.4.5
• 4e64f6b Merge pull request #135 from Byron/fix-linux-launchers
• c88759b auto-review
• 42a34b0 fix(unix): check that_detached launchers for immediate failures
• 279c1b2 fix(unix): restore launcher fallback and support Plasma 6
• See full diff in compare view

Updates similar from 3.2.0 to 3.2.1

Changelog

Sourced from similar's changelog.

3.2.1

• Improved real-world diffing performance substantially without changing the produced diffs. On a corpus of real source file revisions, line diffs run about 4x faster with Algorithm::Myers, 5x faster with Algorithm::Histogram, and 2.5x faster with Algorithm::Patience; word diffs run about 2x faster. This comes from a faster line tokenizer, a SipHash-1-3 content hash that consumes whole words (randomly keyed with std), cheaper integer-keyed lookup tables, hashing only the changed middle of Myers line diffs, flat occurrence tables in Histogram, and a gap buffer in the compaction pass that was quadratic on diffs with many ops. Allocation counts and peak memory dropped as well; in particular one sided and heavily unbalanced inputs no longer build index structures proportional to the larger side for Algorithm::Hunt, Algorithm::Histogram, and Algorithm::Patience.
• Fixed Algorithm::Histogram overflowing the stack on inputs with many scattered changes. Pending ranges are now tracked on the heap, so stack usage no longer grows with the number of anchors. #105
• Fixed TextMerge::labels writing carriage returns and newlines verbatim into conflict markers, which let a label add lines to the output that looked like merged content. Line terminators in labels are now replaced with spaces. #101

Commits

• 71d4831 chore(release): prepare 3.2.1
• b61e6c3 test(histogram): skip small stack tests on WASI
• a4ee936 fix(histogram): track pending ranges on the heap
• 96993d9 docs: add runnable example output gallery (#104)
• 1c64280 docs(changelog): describe diff performance and memory improvements
• a3da6ec perf(compact): use a gap buffer for large operation lists
• ce3a403 perf(histogram): reuse indexes and bound unbalanced input allocations
• 2bcae2f perf(myers): skip unchanged hashing and unused split bookkeeping
• 5a5aa8d perf(text): accelerate line and word tokenization
• 80bc240 perf(hash): accelerate content hashing and integer lookups
• Additional commits viewable in compare view

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 68.20%. Comparing base (1feb2d3) to head (e05e134).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1944   +/-   ##
=======================================
  Coverage   68.20%   68.20%           
=======================================
  Files          43       43           
  Lines        8744     8744           
=======================================
  Hits         5964     5964           
  Misses       2780     2780           

Flag	Coverage Δ
unittests	68.20% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.