Merge branch 'main' into enable-csp

.github/ISSUE_TEMPLATE/bug_report.md → .github/ISSUE_TEMPLATE/bug-report.md

@@ -1,5 +1,5 @@
 ---
-name: 🐛 Bug report
+name: 🐛 Bug Report
 about: Create a report to help us improve
 title: ''
 labels: 'bug,triage'

.github/ISSUE_TEMPLATE/feature_request.md → .github/ISSUE_TEMPLATE/feature-request.md

@@ -1,5 +1,5 @@
 ---
-name: 🙋 Feature request
+name: 🙋 Feature Request
 about: Suggest an idea for this project
 title: ''
 labels: 'enhancement,triage'
@@ -11,6 +11,8 @@ Thanks for filing an issue 😄! Before you submit, please read the following:
 Search open/closed issues before submitting. Someone may have requested the same feature before.
 -->
 
+# 🙋 Feature Request
+
 ## 😯 Problem to Solve
 
 <!--- Provide a clear and concise description of why this feature is wanted or what problem it solves. -->
@@ -19,7 +21,10 @@ Search open/closed issues before submitting. Someone may have requested the same
 
 <!--- Provide a clear and concise description of the feature you're proposing. -->
 
-<!--- The implementing team may build a list of tasks/sub-issues here:
+<!--- The implementing team may build a list of tasks/sub-issues here: -->
+
 ## 📋 Tasks
-- [ ] This is a subtask of the feature. (It can be converted to an issue.)
+
+<!--
+- [ ] This is a subtask of the feature.
 -->

.github/ISSUE_TEMPLATE/ixd_user_story.md → .github/ISSUE_TEMPLATE/interaction-design-request.md

@@ -1,36 +1,37 @@
 ---
-name: 🧑‍💼 Interaction Design (IxD) User story
-about: (PO ONLY) A small chunk of work to be done by an Interaction Designer
+name:  👈 Interaction Design Request
+about: A small chunk of work to be done by an Interaction Designer
 title: 'nimble-{name} interaction design request'
-labels: 'IxD,triage'
+labels: 'interaction design,triage'
 ---
 
 <!-- Ensure the title can be understood without the parent item's context, e.g. "nimble-datepicker interaction design request" rather than just "Interaction Design" -->
 
+# 👈 Interaction Design Request
+
 ## 📌 Request Background
 
 <!-- A short description of the request and requester. E.g. Who is the client and how do they expect to use the component? -->
 <!-- Link to New Component issue -->
 
 ## 🎯 Core Requirements
 
-<!-- Outline the essential requirements of the component. What does the user need to be able to do with the component? E.g. For a date picker… 
-
+<!-- Outline the essential requirements of the component. What does the user need to be able to do with the component? E.g. For a date picker:
+<!--
 - User must to be able to specify a _specific date_ for use in filter query
 - User should not be able to specify an invalid date
 - User must be able to enter date with keyboard interaction alone
-- … -->
+-->
 
 ## 🍆 Non-requirements
 
-<!-- What ideas are out of scope for this component? E.g. For a date picker… 
-
+<!-- What ideas are out of scope for this component? E.g. For a date picker: -->
+<!--
 - User does not need to pick the date from a calendar widget 
-- … -->
-
+-->
 
 ## 🥅 Acceptance Criteria
 
 - [ ] Interaction Design Spec submitted (link)
 - [ ] Interaction Design Spec reviewed by design team
-- [ ] Interaction Design Spec reviewed by dev team
+- [ ] Interaction Design Spec reviewed by dev team

.github/ISSUE_TEMPLATE/new_component.md → .github/ISSUE_TEMPLATE/new-component.md

@@ -1,10 +1,12 @@
 ---
-name: 💡 New component
-about: (DEV TEAM ONLY) New Nimble component
+name: 💡 New Component
+about: New Nimble component
 title: 'nimble-{name} Component'
-labels: 'enhancement'
+labels: 'new component,enhancement,triage'
 ---
 
+# 💡 New Component
+
 ## 😯 Problem to Solve
 
 <!-- List any clients/contacts that specifically need this component, or note that the component just adds general utility. -->
@@ -18,8 +20,7 @@ labels: 'enhancement'
 
 ## 📋 Tasks
 
-<!-- Refer to [CONTR
-IBUTING](https://github.com/ni/nimble/blob/main/packages/nimble-components/CONTRIBUTING.md) for details -->
+<!-- Refer to https://github.com/ni/nimble/blob/main/packages/nimble-components/CONTRIBUTING.md for details -->
 
 - [ ] nimble-{name} interaction design issue
 - [ ] nimble-{name} interaction design spec

.github/ISSUE_TEMPLATE/tech-debt.md

@@ -0,0 +1,8 @@
+---
+name: 🧹 Tech Debt
+about: Non-user-visible improvement to code or development process
+title: ''
+labels: 'tech debt,triage'
+---
+
+# 🧹 Tech Debt

.github/ISSUE_TEMPLATE/visual_design_user_story.md → .github/ISSUE_TEMPLATE/visual-design-request.md

@@ -1,36 +1,37 @@
 ---
-name: 🧑‍🎨 Visual Design (ViD) User story
-about: (DEV TEAM ONLY) A small chunk of work to be done by Visual Designer
+name: 🎨 Visual Design Request
+about: A small chunk of work to be done by Visual Designer
 title: 'nimble-{name} visual design request'
-labels: 'ViD,triage'
+labels: 'visual design,triage'
 ---
 
 <!-- Ensure the title can be understood without the parent item's context, e.g. "nimble-datepicker Visual Design" rather than just "Visual Design" -->
 
+# 🎨 Visual Design Request
+
 ## 📌 Request Background
 
 <!-- A short description of the request and requester. E.g. Who is the client and how do they expect to use the component? -->
 <!-- Link to Interaction Design spec -->
 
 ## 🎯 Core Requirements
 
-<!-- Outline the essential requirements of the component visual design. What states, variations, or other constraints are required? E.g. For a date picker… 
-
+<!-- Outline the essential requirements of the component visual design. What states, variations, or other constraints are required? E.g. For a date picker: -->
+<!--
 - Component needs block and outline appearances
 - Component needs to fit in an editable table cell and in a details panel 
 - Reuse the existing calendar icon
-- … -->
+-->
 
 ## 🍆 Non-requirements
 
-<!-- What ideas are out of scope for this component? E.g. For a date picker… 
-
+<!-- What ideas are out of scope for this component? E.g. For a date picker: -->
+<!--
 - Component does not need a ghost appearance
-- … -->
-
+-->
 
 ## 🥅 Acceptance Criteria
 
 - [ ] Visual Design Spec submitted (link)
 - [ ] Visual Design Spec reviewed by design team
-- [ ] Visual Design Spec reviewed by dev team
+- [ ] Visual Design Spec reviewed by dev team

.github/renovate.json

@@ -3,50 +3,49 @@
   "extends": [
     "config:base"
   ],
-  "enabledManagers": ["npm", "nuget"],
+  "enabledManagers": ["npm", "nuget", "github-actions"],
   "rebaseWhen": "conflicted",
   "schedule": [
     "monthly"
   ],
   "packageRules": [
     {
-      "matchManagers": ["npm"],
+      "matchManagers": ["npm", "nuget", "github-actions"],
       "enabled": false
     },
     {
-      "groupName": "npm dependencies",
+      "groupName": "npm dependencies lock update only",
       "matchManagers": ["npm"],
-      "rangeStrategy": "update-lockfile",
-      "matchDepTypes": ["dependencies"],
-      "matchPackagePatterns":[
-        "^@microsoft/fast",
-        "^@tanstack/",
-        "^@tiptap/",
-        "@types/markdown-it",
-        "comlink",
-        "d3-",
-        "prosemirror-"
-      ],
+      "rangeStrategy": "in-range-only",
+      "matchDepTypes": ["dependencies", "devDependencies", "peerDependencies"],
       "enabled": true
     },
     {
-      "groupName": "npm dev dependencies",
+      "groupName": "npm dependencies update to latest",
       "matchManagers": ["npm"],
       "rangeStrategy": "update-lockfile",
-      "matchDepTypes": ["devDependencies"],
-      "matchPackagePatterns":[
-        "^@ni/eslint-config",
-        "beachball",
-        "storybook"
+      "matchDepTypes": ["dependencies", "devDependencies", "peerDependencies"],
+      "excludePackagePatterns":[
+        "^@angular",
+        "@microsoft/fast-foundation",
+        "@microsoft/fast-react-wrapper",
+        "comlink",
+        "ng-packagr",
+        "playwright",
+        "remark-gfm",
+        "typescript",
+        "zone.js"
       ],
       "enabled": true
     },
     {
-      "groupName": "nuget bunit dependencies",
+      "groupName": "nuget dependencies",
       "matchManagers": ["nuget"],
-      "matchPackagePatterns":[
-        "^bunit"
-      ],
+      "enabled": true
+    },
+    {
+      "groupName": "github actions dependencies",
+      "matchManagers": ["github-actions"],
       "enabled": true
     }
   ]

.github/workflows/dependency-review.yml

@@ -0,0 +1,17 @@
+name: 'Dependency Review'
+on: [pull_request]
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  dependency-review:
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout Repository'
+        uses: actions/checkout@v4
+      - name: 'Dependency Review'
+        uses: actions/dependency-review-action@v4
+        with:
+          comment-summary-in-pr: on-failure