Merge pull request #115 from github/dependabot/github_actions/super-l…

…inter/super-linter-7.0.0

chore(deps): bump super-linter/super-linter from 6.8.0 to 7.0.0

.github/linters/.jscpd.json

@@ -1,7 +1,5 @@
 {
   "threshold": 25,
-  "ignore": [
-    "test*"
-  ],
+  "ignore": ["test*"],
   "absolute": true
-}
+}

.github/pull_request_template.md

@@ -1,5 +1,6 @@
 # Pull Request
-<!-- 
+
+<!--
 PR title needs to be prefixed with a conventional commit type
 (build,chore,ci,docs,feat,fix,perf,refactor,revert,style,test)
 
@@ -9,6 +10,7 @@ examples: "feat: add new logger" or "fix: remove unused imports"
 -->
 
 ## Proposed Changes
+
 <!-- Describe what the changes are and link to a GitHub Issue if one exists -->
 
 ## Readiness Checklist

.github/release-drafter.yml

@@ -1,68 +1,68 @@
 ---
-name-template: 'v$RESOLVED_VERSION'
-tag-template: 'v$RESOLVED_VERSION'
+name-template: "v$RESOLVED_VERSION"
+tag-template: "v$RESOLVED_VERSION"
 template: |
   # Changelog
   $CHANGES
 
   See details of [all code changes](https://github.com/github/automatic-contrib-prs/compare/$PREVIOUS_TAG...v$RESOLVED_VERSION) since previous release
 
 categories:
-  - title: '🚀 Features'
+  - title: "🚀 Features"
     labels:
-      - 'feature'
-      - 'enhancement'
-  - title: '🐛 Bug Fixes'
+      - "feature"
+      - "enhancement"
+  - title: "🐛 Bug Fixes"
     labels:
-      - 'fix'
-      - 'bugfix'
-      - 'bug'
-  - title: '🧰 Maintenance'
+      - "fix"
+      - "bugfix"
+      - "bug"
+  - title: "🧰 Maintenance"
     labels:
-      - 'infrastructure'
-      - 'automation'
-      - 'documentation'
-      - 'dependencies'
-      - 'maintenance'
-      - 'revert'
-  - title: '🏎 Performance'
-    label: 'performance'
-change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
+      - "infrastructure"
+      - "automation"
+      - "documentation"
+      - "dependencies"
+      - "maintenance"
+      - "revert"
+  - title: "🏎 Performance"
+    label: "performance"
+change-template: "- $TITLE @$AUTHOR (#$NUMBER)"
 version-resolver:
   major:
     labels:
-      - 'breaking'
+      - "breaking"
   minor:
     labels:
-      - 'enhancement'
-      - 'fix'
+      - "enhancement"
+      - "fix"
   patch:
     labels:
-      - 'documentation'
-      - 'maintenance'
+      - "documentation"
+      - "maintenance"
   default: patch
 autolabeler:
-  - label: 'automation'
+  - label: "automation"
     title:
-      - '/^(build|ci|perf|refactor|test).*/i'
-  - label: 'enhancement'
+      - "/^(build|ci|perf|refactor|test).*/i"
+  - label: "enhancement"
     title:
-      - '/^(style).*/i'
-  - label: 'documentation'
+      - "/^(style).*/i"
+  - label: "documentation"
     title:
-      - '/^(docs).*/i'
-  - label: 'feature'
+      - "/^(docs).*/i"
+  - label: "feature"
     title:
-      - '/^(feat).*/i'
-  - label: 'fix'
+      - "/^(feat).*/i"
+  - label: "fix"
     title:
-      - '/^(fix).*/i'
-  - label: 'infrastructure'
+      - "/^(fix).*/i"
+  - label: "infrastructure"
     title:
-      - '/^(infrastructure).*/i'
-  - label: 'maintenance'
+      - "/^(infrastructure).*/i"
+  - label: "maintenance"
     title:
-      - '/^(chore|maintenance).*/i'
-  - label: 'revert'
+      - "/^(chore|maintenance).*/i"
+  - label: "revert"
     title:
-      - '/^(revert).*/i'
+      - "/^(revert).*/i"

.github/workflows/auto-labeler.yml

@@ -4,7 +4,7 @@ name: Auto Labeler
 on:
   # pull_request_target event is required for autolabeler to support all PRs including forks
   pull_request_target:
-    types: [ opened, reopened, edited, synchronize ]
+    types: [opened, reopened, edited, synchronize]
 
 permissions:
   contents: read

.github/workflows/docker-image.yml

@@ -3,9 +3,9 @@ name: Docker Image CI
 
 on:
   push:
-    branches: [ main ]
+    branches: [main]
   pull_request:
-    branches: [ main ]
+    branches: [main]
 
 permissions:
   contents: read

.github/workflows/pr-title.yml

@@ -4,7 +4,7 @@ name: "Lint PR Title"
 
 on:
   pull_request_target:
-    types: [ opened, edited, edited, synchronize ]
+    types: [opened, edited, edited, synchronize]
 
 permissions:
   contents: read

.github/workflows/python-ci.yml

@@ -3,9 +3,9 @@ name: Python package
 
 on:
   push:
-    branches: [ main ]
+    branches: [main]
   pull_request:
-    branches: [ main ]
+    branches: [main]
 
 permissions:
   contents: read
@@ -15,7 +15,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ['3.10', '3.11', '3.12']
+        python-version: ["3.10", "3.11", "3.12"]
 
     steps:
       - uses: actions/checkout@692973e3d937129bcbf40652eb9f2f61becf3332 # v4.1.7

.github/workflows/release.yml

@@ -4,8 +4,8 @@ name: Release
 on:
   workflow_dispatch:
   pull_request_target:
-    types: [ closed ]
-    branches: [ main ]
+    types: [closed]
+    branches: [main]
 
 permissions:
   contents: read

.github/workflows/scorecard.yml

@@ -9,9 +9,9 @@ on:
   # To guarantee Maintained check is occasionally updated. See
   # https://github.com/ossf/scorecard/blob/main/docs/checks.md#maintained
   schedule:
-    - cron: '29 11 * * 6'
+    - cron: "29 11 * * 6"
   push:
-    branches: [ main ]
+    branches: [main]
 
 permissions: read-all
 

.github/workflows/stale.yaml

@@ -1,7 +1,7 @@
-name: 'Close stale issues'
+name: "Close stale issues"
 on:
   schedule:
-    - cron: '30 1 * * *'
+    - cron: "30 1 * * *"
 permissions:
   contents: read
 jobs:
@@ -13,8 +13,8 @@ jobs:
     steps:
       - uses: actions/stale@28ca1036281a5e5922ead5184a1bbf96e5fc984e # v9
         with:
-          stale-issue-message: 'This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days.'
-          close-issue-message: 'This issue was closed because it has been stalled for 35 days with no activity.'
+          stale-issue-message: "This issue is stale because it has been open 21 days with no activity. Remove stale label or comment or this will be closed in 14 days."
+          close-issue-message: "This issue was closed because it has been stalled for 35 days with no activity."
           days-before-stale: 21
           days-before-close: 14
           days-before-pr-close: -1

.github/workflows/super-linter.yml

@@ -3,7 +3,7 @@ name: Lint Code Base
 
 on:
   pull_request:
-    branches: [ main ]
+    branches: [main]
 
 permissions:
   contents: read
@@ -28,7 +28,7 @@ jobs:
           python -m pip install --upgrade pip
           pip install -r requirements.txt -r requirements-test.txt
       - name: Lint Code Base
-        uses: super-linter/super-linter@b4515bd4ad9d0aa4681960e053916ab991bdbe96
+        uses: super-linter/super-linter@02a1172d274f021e4c70f66e23f1085eadd1064b
         env:
           DEFAULT_BRANCH: main
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.vscode/launch.json

@@ -1,12 +1,12 @@
 {
-    "version": "0.2.0",
-    "configurations": [
-        {
-            "name": "Python: Current File",
-            "type": "python",
-            "request": "launch",
-            "program": "${file}",
-            "console": "integratedTerminal"
-        }
-    ]
+  "version": "0.2.0",
+  "configurations": [
+    {
+      "name": "Python: Current File",
+      "type": "python",
+      "request": "launch",
+      "program": "${file}",
+      "console": "integratedTerminal"
+    }
+  ]
 }

CODE_OF_CONDUCT.md

@@ -1,5 +1,7 @@
 # Contributor Covenant Code of Conduct
+
 <!-- textlint-disable -->
+
 ## Our Pledge
 
 We as members, contributors, and leaders pledge to make participation in our
@@ -17,23 +19,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-* Demonstrating empathy and kindness toward other people
-* Being respectful of differing opinions, viewpoints, and experiences
-* Giving and gracefully accepting constructive feedback
-* Accepting responsibility and apologizing to those affected by our mistakes,
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-* Focusing on what is best not just for us as individuals, but for the
+- Focusing on what is best not just for us as individuals, but for the
   overall community
 
 Examples of unacceptable behavior include:
 
-* The use of sexualized language or imagery, and sexual attention or
+- The use of sexualized language or imagery, and sexual attention or
   advances of any kind
-* Trolling, insulting or derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or email
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
   address, without their explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
+- Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -106,7 +108,7 @@ Violating these terms may lead to a permanent ban.
 ### 4. Permanent Ban
 
 **Community Impact**: Demonstrating a pattern of violation of community
-standards, including sustained inappropriate behavior,  harassment of an
+standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
 **Consequence**: A permanent ban from any sort of public interaction within
@@ -126,4 +128,5 @@ enforcement ladder](https://github.com/mozilla/diversity).
 For answers to common questions about this code of conduct, see the FAQ at
 [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are available at
 [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations).
+
 <!-- textlint-enable -->

CONTRIBUTING-template.md

@@ -1,12 +1,14 @@
 <!-- markdownlint-disable MD013 -->
 <!-- omit in toc -->
+
 # Contributing to Project-Name
 
 First off, thanks for taking the time to contribute! :heart:
 
 All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us project owners and smooth out the experience for all involved. The team looks forward to your contributions. :tada:
 
 <!-- omit in toc -->
+
 ## Table of Contents
 
 - [I Have a Question](#i-have-a-question)
@@ -35,6 +37,7 @@ We will then take care of the issue as soon as possible.
 ## Reporting Bugs
 
 <!-- omit in toc -->
+
 ### Before Submitting a Bug Report
 
 A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
@@ -50,13 +53,14 @@ A good bug report shouldn't leave others needing to chase you up for more inform
 - Can you reliably reproduce the issue? And can you also reproduce it with older versions?
 
 <!-- omit in toc -->
+
 ### How Do I Submit a Good Bug Report?
 
 We use GitHub issues to track bugs and errors. If you run into an issue with the project:
 
 - Open an [Issue](https://github.com/github/Project-Name/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
 - Explain the behavior you would expect and the actual behavior.
-- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
+- Please provide as much context as possible and describe the _reproduction steps_ that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
 - Provide the information you collected in the previous section.
 
 Once it's filed:
@@ -70,6 +74,7 @@ Once it's filed:
 This section guides you through submitting an enhancement suggestion for Project-Name, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
 
 <!-- omit in toc -->
+
 ### Before Submitting an Enhancement
 
 - Make sure that you are using the latest version.
@@ -78,6 +83,7 @@ This section guides you through submitting an enhancement suggestion for Project
 - Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature or to develop the feature yourself and contribute it to the project.
 
 <!-- omit in toc -->
+
 ### How Do I Submit a Good Enhancement Suggestion?
 
 Enhancement suggestions are tracked as [GitHub issues](https://github.com/github/Project-Name/issues).