From e45a358de07ce438556dc23127e315c9a0bcd7bc Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Sun, 1 Sep 2024 09:20:10 -0500
Subject: [PATCH] [create-pull-request] automated change (#4594)

Co-authored-by: thebentern <9000580+thebentern@users.noreply.github.com>
---
 protobufs                               | 2 +-
 src/mesh/generated/meshtastic/mesh.pb.h | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/protobufs b/protobufs
index 28492e88e..5f7c91adb 160000
--- a/protobufs
+++ b/protobufs
@@ -1 +1 @@
-Subproject commit 28492e88e515aabf5c886dd23631518d6dee82d7
+Subproject commit 5f7c91adb97187e0cb2140de7057344d93444bd1
diff --git a/src/mesh/generated/meshtastic/mesh.pb.h b/src/mesh/generated/meshtastic/mesh.pb.h
index a711da806..9d7ff74a1 100644
--- a/src/mesh/generated/meshtastic/mesh.pb.h
+++ b/src/mesh/generated/meshtastic/mesh.pb.h
@@ -350,6 +350,9 @@ typedef enum _meshtastic_MeshPacket_Priority {
     /* If priority is unset but the message is marked as want_ack,
  assume it is important and use a slightly higher priority */
     meshtastic_MeshPacket_Priority_RELIABLE = 70,
+    /* If priority is unset but the packet is a response to a request, we want it to get there relatively quickly.
+ Furthermore, responses stop relaying packets directed to a node early. */
+    meshtastic_MeshPacket_Priority_RESPONSE = 80,
     /* Higher priority for specific message types (portnums) to distinguish between other reliable packets. */
     meshtastic_MeshPacket_Priority_HIGH = 100,
     /* Ack/naks are sent with very high priority to ensure that retransmission