Skip to content

chore(deps): bump github.com/pilot-protocol/pilotprotocol from 1.14.0 to 1.16.0 - #50

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/pilot-protocol/pilotprotocol-1.16.0
Closed

chore(deps): bump github.com/pilot-protocol/pilotprotocol from 1.14.0 to 1.16.0#50
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/go_modules/github.com/pilot-protocol/pilotprotocol-1.16.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 10, 2026

Copy link
Copy Markdown
Contributor

Bumps github.com/pilot-protocol/pilotprotocol from 1.14.0 to 1.16.0.

Release notes

Sourced from github.com/pilot-protocol/pilotprotocol's releases.

v1.16.0

What's Changed

Full Changelog: pilot-protocol/pilotprotocol@v1.15.0...v1.16.0

v1.15.0

What's Changed

New Contributors

Full Changelog: pilot-protocol/pilotprotocol@v1.14.1...v1.15.0

v1.15.0-rc.1

What's Changed

New Contributors

Full Changelog: pilot-protocol/pilotprotocol@v1.14.1...v1.15.0-rc.1

v1.14.1

What's Changed

Full Changelog: pilot-protocol/pilotprotocol@v1.14.0...v1.14.1

v1.14.1-rc.1

What's Changed

... (truncated)

Changelog

Sourced from github.com/pilot-protocol/pilotprotocol's changelog.

Changelog

All notable changes to Pilot Protocol are recorded here. This file follows Keep a Changelog conventions. The project uses Semantic Versioning.

Detailed per-release notes are on the GitHub Releases page.

[Unreleased]

Added

  • pilotctl send-message can take its payload from stdin or a file: --data - and --data-file <path>. A payload passed as an argument is capped by the OS — a 1 MB --data failed with "Argument list too long", and on Linux a single argument stops at 128 KiB — which is why senders of large bodies needed a separate stdin helper. --data - now means stdin, so a message that is just - has to come from --data-file. One message can carry up to the 64 MiB data-exchange frame limit; a larger payload is refused before anything is sent.
  • A client can ask the daemon whether a datagram was actually sent. The IPC SendTo command is fire-and-forget: when the daemon could not send a datagram (no route to the node, port policy, ephemeral ports exhausted) it only logged IPC datagram send failed, and pilotctl dgram and the driver's SendTo still reported success. A new command pair, CmdSendToConfirm (0x39) / CmdSendToOK (0x3A), sends the same datagram and replies OK once it is handed to the tunnel, or with the error. The daemon lists dgram_confirm in the info reply's features. The existing SendTo command is unchanged and still never replies, so current clients and SDKs are unaffected. The driver's SendToConfirmed (common v0.6.1) uses it, and so does pilotctl dgram: a datagram the daemon refuses fails the command with the reason, an answer that does not come in time says the outcome is unknown, and against an older daemon it sends the old way and reports "confirmed": false.
  • pilotctl send-message --wait can match the reply by message ID. The wait takes the oldest new message from the peer, so two concurrent requests to one peer, or anything else the peer sends in the window, can hand a caller another request's answer. Every message is now sent with a new message ID (message_id in the --json result, and in the receiver's inbox record). A reply whose reply_to is that ID is matched exactly, and a message whose reply_to names another request is never taken. Exact matching needs the responder to echo the request's message_id as reply_to, which no service responder does yet. An untagged reply still works: it is matched by sender and arrival time and taken as soon as it arrives, as before, so for such responders concurrent waits can still be crossed. From a peer known to echo IDs (one of its newest messages in the inbox carries a reply_to) an untagged message is held back until 0.75 s after it arrived, in case the reply naming the request follows; the inbox is searched for that history beside the send, not before it. Once the peer has been seen naming another request in reply_to during the wait,

... (truncated)

Commits
  • 1fbd7e3 Stream segments fit one packet; loss recovery and short writes that work with...
  • 5cfdbd3 daemon: relayed trust handshakes complete in seconds instead of two minutes (...
  • 07e465e deps: common v0.6.0 (#504)
  • 6209914 deps: dataexchange v0.3.0, eventstream v0.3.0, handshake v0.3.0 (#503)
  • 4e5b1fe daemon: report the real endpoint on a private network and keep -advertise-end...
  • 1503f88 Fix datagram port leak, 40ms stream stalls and several pilotctl failure paths...
  • 72f1918 daemon: a datagram send the client can get an answer to (#494)
  • ae1817d daemon: per-source SYN limit allows a burst of 64 and is checked before the s...
  • 795f3ca deps: app-store v1.0.5, beacon v0.2.10, updater v0.2.6 (#489)
  • ee99dd0 fix(appstore): uninstall . no longer removes every installed app (#488)
  • Additional commits viewable in compare view

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)

@dependabot
chore(deps): bump github.com/pilot-protocol/pilotprotocol
265fc02 
Bumps [github.com/pilot-protocol/pilotprotocol](https://github.com/pilot-protocol/pilotprotocol) from 1.14.0 to 1.16.0.
- [Release notes](https://github.com/pilot-protocol/pilotprotocol/releases)
- [Changelog](https://github.com/pilot-protocol/pilotprotocol/blob/main/CHANGELOG.md)
- [Commits](pilot-protocol/pilotprotocol@v1.14.0...v1.16.0)

---
updated-dependencies:
- dependency-name: github.com/pilot-protocol/pilotprotocol
  dependency-version: 1.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Oct 10, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies, go. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@codecov

codecov Bot commented Oct 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@dependabot @github

dependabot Bot commented on behalf of github Oct 17, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #52.

@dependabot dependabot Bot closed this Oct 17, 2026
@dependabot
dependabot Bot deleted the dependabot/go_modules/github.com/pilot-protocol/pilotprotocol-1.16.0 branch October 17, 2026 08:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants