Merge branch 'main' into fluid-input-label

.all-contributorsrc

@@ -904,6 +904,42 @@
       "contributions": [
         "code"
       ]
+    },
+    {
+      "login": "torresga",
+      "name": "G. Torres",
+      "avatar_url": "https://avatars.githubusercontent.com/u/6892410?v=4",
+      "profile": "http://torresga.github.io/",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "FionaDL",
+      "name": "Fiona",
+      "avatar_url": "https://avatars.githubusercontent.com/u/28625558?v=4",
+      "profile": "https://github.com/FionaDL",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "kindoflew",
+      "name": "kindoflew",
+      "avatar_url": "https://avatars.githubusercontent.com/u/70274722?v=4",
+      "profile": "https://lewisdavanzo.com/",
+      "contributions": [
+        "code"
+      ]
+    },
+    {
+      "login": "mgueyraud",
+      "name": "Mario Gueyraud",
+      "avatar_url": "https://avatars.githubusercontent.com/u/9916318?v=4",
+      "profile": "https://github.com/mgueyraud",
+      "contributions": [
+        "code"
+      ]
     }
   ],
   "commitConvention": "none"

.github/CONTRIBUTING.md

@@ -339,14 +339,12 @@ work:
 ### If I'm contributing code, am I required to contribute it for all frameworks?
 
 If you've been working with Carbon for a while, you know that we have code
-assets in vanilla JS, React, Vue and Angular. While the core team only maintains
-the vanilla and React components, we work closely with the Vue and Angular teams
-to maintain parity. The core team also develops with a React first approach,
-which means that our vanilla components will never be ahead of React, though it
-may not be true for the other way around. If you're contributing a bug fix in a
-vanilla component which also exists in the React version, you can either
-contribute a fix for the React version as well or open an issue so that we can
-update the React component accordingly.
+assets in multiple frameworks. While the core team only maintains the React
+components, we work closely with the other framework teams to maintain parity.
+If you're contributing a bug fix in a framework other than React for a component
+which also exists in the React version, you can either contribute a fix for the
+React version as well or open an issue so that we can update the React component
+accordingly.
 
 ### How can I test-drive components or provide a bug reproduction?
 

.github/ISSUE_TEMPLATE/BUG_REPORT.yaml

@@ -70,6 +70,19 @@ body:
       placeholder: What did you see? What did you expect to see?
     validations:
       required: true
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Suggested Severity
+      description:
+        'Read more to understand our [severity levels](https://github.com/carbon-design-system/carbon/blob/main/docs/guides/support.md#severity)'
+      options:
+        - 'Severity 1 = Must be fixed ASAP. The response must be swift. Someone from the team must drop all current work and be immediately reassigned to address the issue.'
+        - 'Severity 2 = User cannot complete task, and/or no workaround within the user experience of a given component.'
+        - 'Severity 3 = User can complete task, and/or has a workaround within the user experience of a given component.'
+        - 'Severity 4 = Unrelated to a user task, has a workaround or does not need a workaround.'
+    validations:
+      required: true
   - type: input
     id: example-url
     attributes:

.github/ISSUE_TEMPLATE/FEATURE_REQUEST_OR_ENHANCEMENT.yaml

@@ -13,57 +13,38 @@ body:
         an existing feature. If you are reporting a bug or problem, please use
         the bug template instead.
   - type: textarea
-    id: summary
+    id: problem
     attributes:
-      label: Summary
+      label: The problem
       description:
-        'Please describe your request in one or two sentences. Clarify if you
-        are asking for design, development, or both design and development.'
+        'Provide a clear and concise description of what the problem this new feature is trying to solve. (For example, I find it frustrating when...). Be sure to attach screenshots or videos to illustrate the problem.'
     validations:
       required: true
   - type: textarea
-    id: justification
+    id: solution
     attributes:
-      label: Justification
-      description: 'Provide the business reasons for this request.'
+      label: The solution
+      description: 'Provide a clear and concise description of what you would like to happen instead. Be sure to attach screenshots or videos to illustrate the solution if possible. Design specs are highly encouraged.'
     validations:
       required: true
   - type: textarea
-    id: Screenshots
+    id: user-research
     attributes:
-      label: Screenshots
-      description: 'Provide screenshots or a screen capture video of the proposed idea, or what you are unable to accomplish that this enhancement would make possible.'
-    validations:
-      required: true
-  - type: textarea
-    id: metrics
-    attributes:
-      label: Desired UX and success metrics
-      description:
-        'Describe the full user experience for this feature. Also define the
-        metrics by which we can measure success/failure for the user.'
-  - type: textarea
-    id: functionality
-    attributes:
-      label: Required functionality
-      description:
-        'Highlight any must have needs and functionality for the request. This
-        should not be a full list of functionality; the Carbon team will work
-        with you to define functionality based on the desired UX.'
-  - type: textarea
-    id: timeline
-    attributes:
-      label: Specific timeline issues / requests
-      description:
-        'Do you want this work within a specific time period? Is it related to
-        an upcoming release?'
+      label: Examples
+      description: Provide sample content, references, or audits of solutions solving the same problem in other applications/websites.
   - type: input
-    id: team
+    id: application
     attributes:
-      label: Your team
-      description: 'Please provide the requesting team you are apart of. @mention design and development members from your team that should be aware of this request.'
-    validations:
-      required: true
+      label: Application/PAL
+      description: "What application and/or PAL do you work on?"
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Business priority
+      options:
+        - 'High Priority = pressing release'
+        - 'Medium Priority = upcoming release but is not pressing'
+        - 'Low Priority = release date is not dependent on fix or not upcoming'
   - type: input
     id: resources
     attributes:
@@ -74,7 +55,7 @@ body:
       value:
         '_Carbon is a collaborative system. We encourage teams to build
         components and submit them for integration as either add-ons or core
-        components._'
+        components. To better understand our feature request process and what happends after you submit this issue, [check out the docs](https://github.com/carbon-design-system/carbon/blob/main/docs/guides/support.md#type-enhancement-) on Github._'
   - type: checkboxes
     id: terms
     attributes:

.github/ISSUE_TEMPLATE/QUESTION.yaml

@@ -30,7 +30,7 @@ body:
   - type: markdown
     attributes:
       value:
-        "For non-IBMer's, you can ask a question on our [Github Discussions
+        "For non-IBMer's, you can ask a question on our [GitHub Discussions
         board](https://github.com/carbon-design-system/carbon/discussions/new)
         or join [our Discord server](https://discord.gg/KAECRaWdzE) to chat with
         Carbon maintainers and fellow community members."

.github/workflows/ci.yml

@@ -94,7 +94,7 @@ jobs:
           key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
       - name: Install dependencies
         run: yarn install --immutable --immutable-cache
-      - uses: dorny/paths-filter@v2.10.2
+      - uses: dorny/paths-filter@v2.11.1
         id: filter
         with:
           filters: |

.github/workflows/release-notifications.yml

@@ -0,0 +1,22 @@
+name: Release Notifications
+
+on:
+  workflow_dispatch:
+  release:
+    types: [released]
+
+jobs:
+  post-comments:
+    name: Post notification comments on PRs
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@main
+      - name: Add release information on pull requests
+        uses: ./actions/release-notifications
+        with:
+          GITHUB_TOKEN: ${{ secrets.GH_BOT_TOKEN }}
+          OWNER: 'carbon-design-system'
+          REPO_NAME: 'carbon'
+          enabled: true
+        env:
+          ACCESS_TOKEN: ${{ secrets.ACCESS_TOKEN }}

.github/workflows/slack-office-hours.yml

@@ -12,7 +12,7 @@ jobs:
     steps:
       - name: Send custom JSON data to Slack workflow
         id: slack
-        uses: slackapi/slack-github-action@v1.22.0
+        uses: slackapi/slack-github-action@v1.23.0
         with:
           payload: |
             {

.github/workflows/v10-ci.yml

@@ -101,7 +101,7 @@ jobs:
           key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
       - name: Install dependencies
         run: yarn install --immutable --immutable-cache
-      - uses: dorny/paths-filter@v2.10.2
+      - uses: dorny/paths-filter@v2.11.1
         id: filter
         with:
           filters: |

.nvmrc

@@ -1 +1 @@
-16.17
+16.18