Update PRs (#5448)

pull-requests/hyperledger-labs/fabric-operations-console.md

@@ -270,33 +270,3 @@ Prevents users with only the reader role from doing actions like:
     </div>
 </div>
 
-<div>
-    <table>
-        <tr>
-            <td>
-                PR <a href="https://github.com/hyperledger-labs/fabric-operations-console/pull/557" class=".btn">#557</a>
-            </td>
-            <td>
-                <b>
-                    prevent the last manager from removing manager role
-                </b>
-            </td>
-        </tr>
-        <tr>
-            <td>
-                
-            </td>
-            <td>
-                #### Type of change
-
-<!--- What type of change? Pick one option and delete the others. -->
-
-- Bug fix
-            </td>
-        </tr>
-    </table>
-    <div class="right-align">
-        Created At 2023-11-09 09:16:14 +0000 UTC
-    </div>
-</div>
-

pull-requests/hyperledger-labs/fabric-token-sdk.md

@@ -38,29 +38,3 @@ Note that the code assumes that tokens stored via `StoreFabToken` are always 'mi
     </div>
 </div>
 
-<div>
-    <table>
-        <tr>
-            <td>
-                PR <a href="https://github.com/hyperledger-labs/fabric-token-sdk/pull/515" class=".btn">#515</a>
-            </td>
-            <td>
-                <b>
-                    enhance VerifyCertifications to return processed certifications
-                </b>
-            </td>
-        </tr>
-        <tr>
-            <td>
-                
-            </td>
-            <td>
-                <nil>
-            </td>
-        </tr>
-    </table>
-    <div class="right-align">
-        Created At 2023-11-09 10:25:47 +0000 UTC
-    </div>
-</div>
-

pull-requests/hyperledger-labs/hlf-connector.md

@@ -14,37 +14,11 @@ permalink: /pull-requests/hyperledger-labs/hlf-connector
     <table>
         <tr>
             <td>
-                PR <a href="https://github.com/hyperledger-labs/hlf-connector/pull/105" class=".btn">#105</a>
+                PR <a href="https://github.com/hyperledger-labs/hlf-connector/pull/106" class=".btn">#106</a>
             </td>
             <td>
                 <b>
-                    Increment version after release
-                </b>
-            </td>
-        </tr>
-        <tr>
-            <td>
-                <span class="chip">auto-version-increment</span>
-            </td>
-            <td>
-                Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action
-            </td>
-        </tr>
-    </table>
-    <div class="right-align">
-        Created At 2023-10-03 14:11:53 +0000 UTC
-    </div>
-</div>
-
-<div>
-    <table>
-        <tr>
-            <td>
-                PR <a href="https://github.com/hyperledger-labs/hlf-connector/pull/104" class=".btn">#104</a>
-            </td>
-            <td>
-                <b>
-                    Minor refactorings to Approvers API
+                    Introduce capability for publishing error Records to Dead letter topic
                 </b>
             </td>
         </tr>
@@ -53,15 +27,19 @@ permalink: /pull-requests/hyperledger-labs/hlf-connector
                 
             </td>
             <td>
-                Follow-up of #102 
-Wrap long request params into Request-Part.
-Change method signature to POST since the operation involves transfer of Files.
-
+                This PR contains the changes for publishing failed consumer Records polled from the Integration topic(s) to a configured error Event listener Topic.
+
+The changes would effectively allow the Connector to publish the Error record to a topic based on the following criteria :-
+
+- If the Event-Listener topic (Block & Chaincode) has the optional field `listenToFailedMessages` set as true, the failed message will be published back to Event listener topic (this is the current behaviour).
+- If the Kafka properties of a dedicated Dead letter topic is configured, the errored message will be published to the configured dead letter topic.
+- If the configuration `listenToFailedMessages` is set to true as well as a dedicated Dead letter topic is configured, the dead letter topic will take priority and record will be dispatched to it.
+- If none of the above options are available, the listener will attempt retries and log the failed record by committing the offset.
             </td>
         </tr>
     </table>
     <div class="right-align">
-        Created At 2023-10-03 13:32:17 +0000 UTC
+        Created At 2023-11-16 09:46:07 +0000 UTC
     </div>
 </div>