From e91f209cc6b4d1faf2f4e95816b7fdd4a793faeb Mon Sep 17 00:00:00 2001
From: "John L." <47447266+aBurmeseDev@users.noreply.github.com>
Date: Fri, 27 Sep 2024 09:08:01 -0700
Subject: [PATCH] chore: update stale-issue bot (#6528)

---
 .github/workflows/stale_issues.yml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/stale_issues.yml b/.github/workflows/stale_issues.yml
index 60b8929e2b2cb..031944638053c 100644
--- a/.github/workflows/stale_issues.yml
+++ b/.github/workflows/stale_issues.yml
@@ -7,14 +7,17 @@ on:
 
 jobs:
   cleanup:
+    permissions:
+      issues: write
+      contents: read
+      pull-requests: write
     runs-on: ubuntu-latest
     name: Stale issue job
     steps:
-    - uses: aws-actions/stale-issue-cleanup@v3
+    - uses: aws-actions/stale-issue-cleanup@v6
       with:
         # Setting messages to an empty string will cause the automation to skip
         # that category
-        ancient-issue-message: Greetings! We’re closing this issue because it has been open a long time and hasn’t been updated in a while and may not be getting the attention it deserves. We encourage you to check if this is still an issue in the latest release and if you find that this is still a problem, please feel free to comment or open a new issue.
         stale-issue-message: This issue has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the issue from automatically closing.
         stale-pr-message: This PR has not received a response in 1 week. If you still think there is a problem, please leave a comment to avoid the PR from automatically closing.
         # These labels are required
@@ -31,7 +34,6 @@ jobs:
         # Issue timing
         days-before-stale: 10
         days-before-close: 4
-        days-before-ancient: 365
 
         # If you don't want to mark a issue as being ancient based on a
         # threshold of "upvotes", you can set this here. An "upvote" is