Release v1.4.0

Author: MKISTM

.github/ISSUE_TEMPLATE.md

@@ -0,0 +1,51 @@
+name: "\U0001F41B Bug Report"
+description: Report a bug in the project
+title: "[Bug]: "
+labels: [bug]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for helping us improve the quality of our software! Please provide as much detail as possible.
+  - type: input
+    id: bug_summary
+    attributes:
+      label: Bug Summary
+      description: Briefly describe the bug.
+      placeholder: "The application crashes when..."
+    validations:
+      required: true
+  - type: textarea
+    id: bug_details
+    attributes:
+      label: Detailed Description
+      description: Provide a detailed description of the bug, including steps to reproduce it.
+    validations:
+      required: true
+  - type: input
+    id: expected-behavior
+    attributes:
+      label: Expected Behavior
+      description: A clear and concise description of what you expected to happen.
+      placeholder: Describe the expected behavior
+  - type: input
+    id: actual-behavior
+    attributes:
+      label: Actual Behavior
+      description: A clear and concise description of what actually happens.
+      placeholder: Describe what actually happened
+  - type: input
+    id: environment
+    attributes:
+      label: Environment
+      description: Describe the environment in which the bug occurs (e.g., board, compiler, IDE, version).
+  - type: dropdown
+    id: severity
+    attributes:
+      label: Severity
+      description: How severe is the bug?
+      options:
+        - Critical
+        - Major
+        - Normal
+        - Minor

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: false
+contact_links:
+  - name: "\U0001F6E1 Report a security vulnerability"
+    about: Please refer to the SECURITY.md file for instructions.
+    url: ./../../SECURITY.md
+  - name: "\U0001F6F1 Request support"
+    about: You can reach out to the ST Community.
+    url: https://community.st.com/s/topiccatalog

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,29 @@
+name: "\U0001F4A1 Feature Request"
+description: Suggest a new feature or enhancement
+title: "[Feature]: "
+labels: [enhancement]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        We appreciate your interest in improving the quality of our software! Please provide details about the feature.
+  - type: input
+    id: feature_summary
+    attributes:
+      label: Feature Summary
+      description: Briefly describe the feature or enhancement.
+      placeholder: "Add support for..."
+    validations:
+      required: true
+  - type: textarea
+    id: feature_details
+    attributes:
+      label: Detailed Description
+      description: Provide a detailed description of the feature, including potential benefits.
+    validations:
+      required: true
+  - type: input
+    id: use_case
+    attributes:
+      label: Use Case
+      description: Describe how this feature will be used and who will benefit from it.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,24 @@
+name: "\U0001F4AC  Question"
+description: Ask a question about the project
+title: "[Question]: "
+labels: [question]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Have a question? We're here to help! Please provide details about your inquiry.
+  - type: input
+    id: question_summary
+    attributes:
+      label: Question Summary
+      description: Briefly describe your question.
+      placeholder: "How do I..."
+    validations:
+      required: true
+  - type: textarea
+    id: question_details
+    attributes:
+      label: Detailed Description
+      description: Provide a detailed description of your question, including any relevant context.
+    validations:
+      required: true

.github/ISSUE_TEMPLATE/question.yml

@@ -55,8 +55,8 @@ further defined and clarified by project maintainers.
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at https://www.st.com/content/st_com/en/contact-us.html. All
-complaints will be reviewed and investigated and will result in a response that
+reported by contacting the project team via this [link](https://www.st.com/content/st_com/en/contact-us.html).
+All complaints will be reviewed and investigated and will result in a response that
 is deemed necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of an incident.
 Further details of specific enforcement policies may be posted separately.
@@ -67,9 +67,7 @@ members of the project's leadership.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org), version 1.4,
 available [here](https://www.contributor-covenant.org/version/1/4/code-of-conduct.html).
 
-[homepage]: https://www.contributor-covenant.org
-
 For answers to common questions about this code of conduct, refer to the FAQ section [here](https://www.contributor-covenant.org/faq).

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,40 +1,46 @@
 # Contributing guide
 
-This guide serves as a checklist before contributing to this repository. It mainly focuses on the steps to follow to submit an issue or a pull-request.
+This guide mainly focuses on the steps to follow to submit an issue or a pull request.
 
 ## 1. Issues
 
 ### 1.1 Before opening an issue
 
-Please check the following points before posting an issue:
-* Make sure you are using the latest commit (major releases are tagged, but corrections are available as new commits).
-* Make sure your issue is a question/feedback/suggestions **related to** the software provided in this repository. Otherwise, please refer to section [3](CONTRIBUTING.md#3-support-requests-and-questions) below.
-* Make sure your issue is not already reported/fixed on GitHub or discussed on a previous issue. Do not forget to browse into the **closed** issues.
+Before posting an issue, please ensure:
+* You are using the latest commit.
+* Your issue is **not** a vulnerability. Otherwise, please refer to section [3](CONTRIBUTING.md#3-vulnerabilities) below.
+* Your issue is **related to** the software provided in this repository. Otherwise, please refer to section [4](CONTRIBUTING.md#4-support-requests-and-miscellaneous) below.
+* Your issue is not already reported, fixed or discussed in a previous one. Remember to browse the **closed** issues.
 
 ### 1.2 Posting the issue
 
-When you have checked the previous points, create a new report from the **Issues** tab of this repository. A template is available [here](../../issues/new/choose) to help you report the issue you are facing or the enhancement you would like to propose.
+When you have checked the previous points, create a new report from the **Issues** tab of this repository. A couple of templates are available [here](../../issues/new/choose).
 
 ## 2. Pull Requests
 
-### 2.1 Before opening a pull-request
+### 2.1 Before opening a pull request
 
 STMicrolectronics is happy to receive contributions from the community, based on an initial Contributor License Agreement (CLA) procedure.
 
-* If you are an individual writing original source code and you are sure **you own the intellectual property**, then you need to sign an Individual [CLA](https://cla.st.com).
-* If you work for a company that wants also to allow you to contribute with your work, your company needs to provide a Corporate [CLA](https://cla.st.com) mentioning your GitHub account name.
+* If you are an individual writing original source code and you are sure **you own the intellectual property**, then you need to sign an **Individual** [CLA](https://cla.st.com).
+* If you work for a company that wants also to allow you to contribute with your work, your company needs to provide a **Corporate** [CLA](https://cla.st.com) mentioning your GitHub account name.
 * If you are not sure that a CLA (Individual or Corporate) has been signed for your GitHub account you can check the [CLA](https://cla.st.com) dedicated page.
 
-Please note that:
-* The Corporate CLA will always take precedence over the Individual CLA.
-* One CLA submission is sufficient, for any project proposed by STMicroelectronics.
+> [!IMPORTANT]
+> Please note that:
+> * The Corporate CLA will always take precedence over the Individual CLA.
+> * One CLA submission is sufficient, for any project proposed by STMicroelectronics.
 
 ### 2.2 How to proceed
 
 * We recommend to engage first a communication thru an issue, in order to present your proposal, just to confirm that it corresponds to STMicroelectronics' domain or scope.
 * Then fork the project to your GitHub account to further develop your contribution. Please use the latest commit version.
-* Please, submit one pull-request per new feature or proposal. This will ease the analysis and the final merge if accepted.
+* Please, submit one pull request per new feature or proposal. This will ease the analysis and the final merge if accepted.
 
-## 3. Support requests and questions
+## 3. Vulnerabilities
 
-For support requests or any other question related to the product, the tools, the environment, you can submit a post to the **ST Community** on the appropriate topic [page](https://community.st.com/t5/stm32-mcus/ct-p/stm32-mcus).
+To report a **vulnerability**, please refer to the [SECURITY.md](./SECURITY.md) file for instructions.
+
+## 4. Support requests and miscellaneous
+
+For support requests or any other topics not related to the content of this repository, you can submit a post to the **ST Community** on the appropriate topic [page](https://community.st.com/s/topiccatalog).