Sync working groups

Author: actions-user

_data/wg.yaml

@@ -1,5 +1,26 @@
 ---
 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: staled
+      lts: false
+      completed: false
+      last-activity: 2025-06-23
+      last-update-date: 2025-03-28
+      last-update: |
+        The working group has now officially started. As the work began before the kick-off, a few items are already in the "completed" state.
+      deliverable: TBD
+      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
+      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Dev Services Lifecycle"
       board-url: "https://github.com/orgs/quarkusio/projects/49"
       short-description: |
@@ -150,27 +171,6 @@ working-groups:
         Marking as risk as deadline april 1st is looming and still things to define. 
         
         There is a Quarkus f2f meeting next week that could clarify/move things forward and start to share more publically as things get moved over from internal IT.
-    - 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: staled
-      lts: false
-      completed: false
-      last-activity: 2025-04-23
-      last-update-date: 2025-03-28
-      last-update: |
-        The working group has now officially started. As the work began before the kick-off, a few items are already in the "completed" state.
-      deliverable: TBD
-      point-of-contact: "@sberyozkin (@_<strong>Sergey Beryozkin</strong>  on Zulip)"
-      proposal: https://github.com/quarkusio/quarkus/discussions/42116
     - title: "Observability.Next"
       board-url: "https://github.com/orgs/quarkusio/projects/42"
       short-description: |