Merge branch 'master' into per_node_endpoint_fixes

Author: cecille

.github/stale.yml

@@ -102,7 +102,6 @@ jobs:
                     # - "-imx"
                     - "-java"
                     - "-k32w"
-                    - "-mbed-os"
                     - "-nrf-platform"
                     - "-telink"
                     - "-ti"

.github/workflows/docker_img.yaml

@@ -38,7 +38,7 @@ jobs:
         if: github.actor != 'restyled-io[bot]'
 
         container:
-            image: ghcr.io/project-chip/chip-build-ameba:54
+            image: ghcr.io/project-chip/chip-build-ameba:68
             options: --user root
 
         steps:

.github/workflows/examples-ameba.yaml

@@ -37,7 +37,7 @@ jobs:
     if: github.actor != 'restyled-io[bot]'
 
     container:
-      image: ghcr.io/project-chip/chip-build-bouffalolab:54
+      image: ghcr.io/project-chip/chip-build-bouffalolab:68
       volumes:
         - "/tmp/bloat_reports:/tmp/bloat_reports"
     steps:

.github/workflows/examples-bouffalolab.yaml

@@ -27,7 +27,7 @@ concurrency:
 
 env:
     CHIP_NO_LOG_TIMESTAMPS: true
-    
+
 jobs:
 
     qemu-esp32:
@@ -75,12 +75,7 @@ jobs:
         name: Tizen
 
         runs-on: ubuntu-latest
-        # NOTE: job temporarely disabled as it seems flaky. The flake does not result in usable
-        #       logs so the current theory is that we run out of space. This is unusual as
-        #       larger docker images succeed at bootstrap, however it needs more investigation
-        #       to detect an exact/real root cause.
-        if: false
-        # if: github.actor != 'restyled-io[bot]'
+        if: github.actor != 'restyled-io[bot]'
 
         container:
             image: ghcr.io/project-chip/chip-build-tizen-qemu:54

.github/workflows/examples-mbed.yaml

@@ -0,0 +1,42 @@
+name: "Process Stale Issues and PRs"
+on:
+    workflow_dispatch:
+    schedule:
+        - cron: "30 1 * * *"
+
+permissions:
+    issues: write
+    pull-requests: write
+
+jobs:
+    stale:
+        runs-on: ubuntu-latest
+        steps:
+            - uses: actions/stale@v9
+              with:
+                  stale-issue-message:
+                      "This issue has been automatically marked as stale because
+                      it has not had recent activity. It will be closed if no
+                      further activity occurs. Remove stale label or comment or
+                      this will be closed in 30 days."
+                  stale-pr-message:
+                      "This pull request has been automatically marked as stale
+                      because it has not had recent activity. It will be closed
+                      if no further activity occurs. Remove stale label or
+                      comment or this will be closed in 10 days."
+                  close-issue-message:
+                      "This stale issue has been automatically closed. Thank you
+                      for your contributions."
+                  close-pr-message:
+                      "This stale pull request has been automatically closed.
+                      Thank you for your contributions."
+                  days-before-issue-stale: 30
+                  days-before-issue-close: -1 # Don't close them for now
+                  days-before-pr-stale: 90
+                  days-before-pr-close: 10
+                  exempt-issue-labels:
+                      "security,blocked,cert blocker,build issue,Spec XML
+                      align,CI/CD improvements,memory"
+                  exempt-pr-labels:
+                      "security,blocked,cert blocker,build issue,Spec XML
+                      align,CI/CD improvements,memory"