🔄 synced file(s) with conda/infrastructure

.github/ISSUE_TEMPLATE/0_bug.yml

@@ -9,7 +9,7 @@ body:
       value: |
         Because processing new bug reports is time-consuming, we would like to ask you to fill out the following form to the best of your ability and as completely as possible.
 
-        > **Note**
+        > [!NOTE]
         > Bug reports that are incomplete or missing information may be closed as inactionable.
 
         Since there are already a lot of open issues, please also take a moment to search existing ones to see if your bug has already been reported. If you find something related, please upvote that issue and provide additional details as necessary.

.github/ISSUE_TEMPLATE/1_feature.yml

@@ -9,7 +9,7 @@ body:
       value: |
         Because processing new feature requests is time-consuming, we would like to ask you to fill out the following form to the best of your ability and as completely as possible.
 
-        > **Note**
+        > [!NOTE]
         > Feature requests that are incomplete or missing information may be closed as inactionable.
 
         Since there are already a lot of open issues, please also take a moment to search existing ones to see if your feature request has already been submitted. If you find something related, please upvote that issue and provide additional details as necessary.

.github/ISSUE_TEMPLATE/epic.yml

@@ -11,7 +11,7 @@ body:
 
         If you are attempting to report a bug, propose a new feature, or some other code change please use one of the other forms available.
 
-        > **Note**
+        > [!NOTE]
         > Epics that are incomplete or missing information may be closed as inactionable.
 
         Since there are already a lot of open issues, please also take a moment to search existing ones to see if a similar epic has already been opened. If you find something related, please upvote that issue and provide additional details as necessary.

.github/workflows/lock.yml

@@ -18,7 +18,7 @@ jobs:
     if: '!github.event.repository.fork'
     runs-on: ubuntu-latest
     steps:
-      - uses: dessant/lock-threads@v4
+      - uses: dessant/lock-threads@v5
         with:
           # Number of days of inactivity before a closed issue is locked
           issue-inactive-days: 365
@@ -42,5 +42,5 @@ jobs:
           # Reason for locking a pull request, value must be one of resolved, off-topic, too heated, spam or ''
           pr-lock-reason: resolved
 
-          # Limit locking to only issues or pull requests, value must be one of issues, prs or ''
-          process-only: ''
+          # Limit locking to issues, pull requests or discussions, value must be a comma separated list of issues, prs, discussions or ''
+          process-only: issues, prs

.github/workflows/stale.yml

@@ -39,7 +39,7 @@ jobs:
         with:
           path: https://raw.githubusercontent.com/conda/infra/main/.github/messages.yml
 
-      - uses: actions/stale@v8
+      - uses: actions/stale@v9
         id: stale
         with:
           # Only issues with these labels are checked whether they are stale

CODE_OF_CONDUCT.md

@@ -1,6 +1,6 @@
 # Conda Organization Code of Conduct
 
-> **Note**
+> [!NOTE]
 > Below is the short version of our CoC, see the long version [here](https://github.com/conda-incubator/governance/blob/main/CODE_OF_CONDUCT.md).
 
 # The Short Version

HOW_WE_USE_GITHUB.md

@@ -43,12 +43,12 @@ This document seeks to outline how we as a community use GitHub Issues to track
     - [Spikes](#spikes)
   - [Working on Issues](#working-on-issues)
 
-> **Note**
+> [!NOTE]
 > This document is written in the style of an FAQ. For easier navigation, use [GitHub's table of contents feature][docs-toc].
 
 ## What is "Issue Sorting"?
 
-> **Note**
+> [!NOTE]
 > "Issue sorting" is similar to that of "triaging", but we've chosen to use different terminology because "triaging" is a word related to very weighty topics (_e.g._, injuries and war) and we would like to be sensitive to those connotations. Additionally, we are taking a more "fuzzy" approach to sorting (_e.g._, severities may not be assigned, etc.).
 
 "Issue Sorting" refers to the process of assessing the priority of incoming issues. Below is a high-level diagram of the flow of issues:
@@ -213,7 +213,7 @@ Below are some boilerplate responses for the most commonly-seen issues to be sor
 This is a duplicate of <b>[link to primary issue]</b>; please feel free to continue the discussion there.
 </pre>
 
-> **Warning**
+> [!WARNING]
 > Apply the https://github.com/conda/infrastructure/labels/duplicate label to the issue being closed and https://github.com/conda/infrastructure/labels/duplicate%3A%3Aprimary to the original issue.
 
 </details>
@@ -244,7 +244,7 @@ If you are still encountering this issue please reopen in the
 where `conda` installer/package issues are addressed.
 </pre>
 
-> **Warning**
+> [!WARNING]
 > Apply the https://github.com/conda/infrastructure/labels/off-topic label to these issues before closing them out.
 
 </details>
@@ -260,7 +260,7 @@ if you continue to experience the problems described here,
 please post details to the [Nucleus forums](https://community.anaconda.cloud/).
 </pre>
 
-> **Warning**
+> [!WARNING]
 > Apply the https://github.com/conda/infrastructure/labels/off-topic label to these issues before closing them out.
 
 </details>