Skip to content

chore(deps): update dorny/paths-filter action to v4#741

Merged
wpfleger96 merged 4 commits into
mainfrom
renovate/dorny-paths-filter-4.x
May 24, 2026
Merged

chore(deps): update dorny/paths-filter action to v4#741
wpfleger96 merged 4 commits into
mainfrom
renovate/dorny-paths-filter-4.x

Conversation

@renovate

@renovate renovate Bot commented May 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
dorny/paths-filter action major v3.0.2v4.0.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

dorny/paths-filter (dorny/paths-filter)

v4.0.1

Compare Source

What's Changed

New Contributors

Full Changelog: dorny/paths-filter@v4.0.0...v4.0.1

v4.0.0

Compare Source

v4

Compare Source

v3.0.3

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot requested a review from a team as a code owner May 23, 2026 22:31
@renovate renovate Bot force-pushed the renovate/dorny-paths-filter-4.x branch from e4c8db2 to aac83da Compare May 23, 2026 23:03
@wpfleger96 wpfleger96 enabled auto-merge (squash) May 23, 2026 23:20
@renovate

renovate Bot commented May 23, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@wpfleger96 wpfleger96 merged commit fa3e0d1 into main May 24, 2026
16 checks passed
@wpfleger96 wpfleger96 deleted the renovate/dorny-paths-filter-4.x branch May 24, 2026 00:32
tlongwell-block pushed a commit that referenced this pull request Jun 5, 2026
Tyler's fork (disable-iroh-relays knobs) merged to upstream main via #782->#736,
which also landed the native Rust SDK and split-readiness doctor. Repin off the
fork back to upstream so we stop maintaining a fork.

Both workspaces repinned: desktop/src-tauri (mesh-llm feature) and the
sprout-relay dev-dependency (used in mesh_signaling tests).

Only API drift: SDK feature 'serve' renamed to 'serving' on main (serving
transitively pulls node+client). Updated both manifests.

Verified against ebc3ab4c with --features mesh-llm:
- sprout-desktop: cargo check + clippy (zero warnings, #741 gate) + full suite (440 passed)
- sprout-relay: full suite incl. mesh_signaling tests (271 passed)

Commit 1 of the mesh unification (PLANS/MESH_IDEAL_ARCHITECTURE.md).

Signed-off-by: npub1qyvc0c5kl4gqv2fd97fsk46tu378sqgy35vc83rvgfwne90sel7s0ed67d <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@sprout-oss.stage.blox.sqprod.co>
tlongwell-block pushed a commit that referenced this pull request Jun 5, 2026
Route the saved/manual relay-mesh start path through the coordinator's
start_client so it publishes a paired connect-request (kind:24621), making the
peer dial back. This is the original flakiness root cause: saved agents did a
one-sided dial into a NAT and never told the peer to dial back, so they could
not hole-punch on restart.

- resolve_mesh_bootstrap_target / pick_serve_target_for_model now return the
  full MeshServeTarget (was just the endpoint addr) so the caller has the
  reporter pubkey to address the 24621.
- ensure_relay_mesh_for_record takes &AppHandle: resolves the live target,
  brings up the local client node (whose status yields our own invite token),
  then start_client(target.reporter_pubkey, target.endpoint_addr, self_addr)
  publishes the 24621 + drives attempt-scoped retry. start_client blocks on the
  listener being active, so the cold-launch race stays closed.
- Degrades gracefully: if the target has no reporter pubkey or we have no invite
  token, the one-sided dial already happened — no worse than old behavior — so
  the connect-request is skipped (logged) rather than failing the spawn.
- Threaded &AppHandle through both callers (restore.rs auto-start, agents.rs
  start_local_agent_with_preflight + its no-mesh stub).
- start_client re-exported; allow(dead_code) markers removed now that it has a
  consumer.

Verified: cargo check (mesh-llm AND default no-feature builds) + clippy (0
warnings, #741 gate) + full sprout-desktop suite (447 passed) against ebc3ab4c.

Commit 4 of the mesh unification (PLANS/MESH_IDEAL_ARCHITECTURE.md).

Signed-off-by: npub1qyvc0c5kl4gqv2fd97fsk46tu378sqgy35vc83rvgfwne90sel7s0ed67d <011987e296fd5006292d2f930b574be47c7801048d1983c46c425d3c95f0cffd@sprout-oss.stage.blox.sqprod.co>
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.

1 participant