Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,28 @@
 ---
 working-groups:
+    - title: "OIDC improvements"
+      board-url: "https://github.com/orgs/quarkusio/projects/46"
+      short-description: |
+        The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
+      readme: |
+        <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
+        <ul>
+        <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)</li>
+        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
+        <li>Deliverable: TBD</li>
+        </ul>
+      status: on track
+      lts: false
+      completed: false
+      last-activity: 2025-10-08
+      last-update-date: 2025-09-08
+      last-update: |
+        In the last month, the WG - OIDC improvements made notable progress by successfully closing an issue related to flow-specific OIDC request/response filter support, enhancing the overall functionality of quarkus-oidc. No new issues were opened during this period, indicating a focused effort on refining existing features and implementing critical security enhancements. The group continues to prioritize its objectives to further improve OIDC request interception and support for JWT bearer client authentication in the authorization code flow.
+        
+        (This status update was automatically generated using AI.)
+      deliverable: TBD
+      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Gizmo 2"
       board-url: "https://github.com/orgs/quarkusio/projects/43"
       short-description: |
@@ -575,29 +598,6 @@ working-groups:
       last-update-date: 2025-07-22
       last-update: |
         The working group has been paused due to a lack of progress for some time now. Let's revisit it in a few months.
-    - title: "OIDC improvements"
-      board-url: "https://github.com/orgs/quarkusio/projects/46"
-      short-description: |
-        The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow
-      readme: |
-        <p>The goal of this working group is to improve quarkus-oidc by: implementing crucial new security features, continuing with improving the way OIDC requests can be intercepted, prioritizing some other open issues, such as using JWT bearer client authentication to complete the authorization code flow</p>
-        <ul>
-        <li>Point of contact: @sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)</li>
-        <li>Proposal: https://github.com/quarkusio/quarkus/discussions/42116</li>
-        <li>Deliverable: TBD</li>
-        </ul>
-      status: on track
-      lts: false
-      completed: false
-      last-activity: 2025-08-21
-      last-update-date: 2025-09-08
-      last-update: |
-        In the last month, the WG - OIDC improvements made notable progress by successfully closing an issue related to flow-specific OIDC request/response filter support, enhancing the overall functionality of quarkus-oidc. No new issues were opened during this period, indicating a focused effort on refining existing features and implementing critical security enhancements. The group continues to prioritize its objectives to further improve OIDC request interception and support for JWT bearer client authentication in the authorization code flow.
-        
-        (This status update was automatically generated using AI.)
-      deliverable: TBD
-      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Quarkus 3.20 LTS"
       board-url: "https://github.com/orgs/quarkusio/projects/41"
       short-description: |