From 696bba4a230b081026550f4acd4e9abf537a0d7b Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:01:23 +0100 Subject: [PATCH 1/7] chore: update CODE_OF_CONDUCT.md file --- CODE_OF_CONDUCT.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 1cf484f1..5a9533d3 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,18 +1,18 @@ -# Contributor Covenant Code of Conduct +# Contributor covenant code of conduct -## Our Pledge +## Pledge -In the interest of fostering an open and welcoming environment, we as -contributors and maintainers pledge to making participation in our -project and our community a harassment-free experience for everyone, -regardless of age, body size, disability, ethnicity, sex -characteristics, gender identity and expression, level of experience, -education, socio-economic status, nationality, personal appearance, -race, religion, or sexual identity and orientation. +In the interest of fostering an open and welcoming environment, +all contributors and maintainers pledge to making participation +in the Ansys project and community a harassment-free experience +for everyone, regardless of age, body size, disability, ethnicity, +sex characteristics, gender identity and expression, level of +experience, education, socioeconomic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. -## Our Standards +## Standards -Examples of behavior that contributes to creating a positive environment +Examples of behavior that contribute to creating a positive environment include: * Using welcoming and inclusive language @@ -32,7 +32,7 @@ Examples of unacceptable behavior by participants include: * Other conduct which could reasonably be considered inappropriate in a professional setting -## Our Responsibilities +## Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in @@ -48,14 +48,14 @@ offensive, or harmful. This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of -representing a project or community include using an official project e-mail -address, posting via an official social media account, or acting as an appointed +representing a project or community include using an official project email +address, posting using an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers. ## Attribution -This Code of Conduct is adapted from the [Contributor Covenant][homepage], +This code of conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html From 0891494da4bd76174db389d210b051c44a9bf7bf Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:01:24 +0100 Subject: [PATCH 2/7] chore: update CONTRIBUTING.md file --- CONTRIBUTING.md | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 827878e0..5d752a14 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,16 +1,12 @@ -# Contributing +# Contribute -We welcome any code contributions and hope that this -guide facilitate an understanding of the PyConceptEV code. -It is important to note that while PyConceptEV -is maintained by Ansys and any submissions are reviewed -thoroughly before merging, we still seek to foster a community that can -support user questions and develop new features to make this library -useful to all. As such, we welcome and encourage any -questions or submissions to this repository. +Overall guidance on contributing to a PyAnsys library appears in the +[Contributing] topic in the *PyAnsys developer's guide*. Ensure that you +are thoroughly familiar with this guide before attempting to contribute to +{project-name}. -For information on contributing to a PyAnsys library, see the [PyAnsys developer's guide]. -For information specific to contributing to PyConceptEV, see [Contribute]. +The following contribution information is specific to {project-name}. -[PyAnsys developer's guide]: https://dev.docs.pyansys.com/index.html -[Contribute]: https://conceptev.docs.pyansys.com/dev/contributing.html +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html + + From 4a1a7b05e57415689bcadc7b281dc5ce51186b63 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:01:26 +0100 Subject: [PATCH 3/7] chore: update SECURITY.md file --- SECURITY.md | 36 +++++++++++------------------------- 1 file changed, 11 insertions(+), 25 deletions(-) diff --git a/SECURITY.md b/SECURITY.md index 5afe0f1e..5a88c014 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -1,30 +1,16 @@ - +> [!CAUTION] +> Do not use GitHub issues to report any security vulnerabilities. -# Security Policy +If you detect a vulnerability, contact the [PyAnsys Core team](mailto:pyansys.core@ansys.com), +mentioning the repository and the details of your finding. The team will address it as soon as possible. -## Reporting a Vulnerability +Provide the PyAnsys Core team with this information: -If you detect a vulnerability, please open an issue on GitHub and add the -``security`` label to your issue. The team will address it as soon as possible. +- Any specific configuration settings needed to reproduce the problem +- Step-by-step guidance to reproduce the problem +- The exact location of the problematic source code, including tag, branch, commit, or a direct URL +- The potential consequences of the vulnerability, along with a description of how an attacker could take advantage of the issue From 0726badeab3e50b15d104eb1a78f7f0625baeb5c Mon Sep 17 00:00:00 2001 From: pyansys-ci-bot <92810346+pyansys-ci-bot@users.noreply.github.com> Date: Sat, 1 Nov 2025 04:02:29 +0000 Subject: [PATCH 4/7] chore: adding changelog file 294.miscellaneous.md [dependabot-skip] --- doc/changelog.d/294.miscellaneous.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/changelog.d/294.miscellaneous.md diff --git a/doc/changelog.d/294.miscellaneous.md b/doc/changelog.d/294.miscellaneous.md new file mode 100644 index 00000000..1d98c690 --- /dev/null +++ b/doc/changelog.d/294.miscellaneous.md @@ -0,0 +1 @@ +CHORE: Update missing or outdated files From c33c8acb4c57896cbb153e3977dfd026ef5b5dbf Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Mon, 1 Dec 2025 05:12:57 +0100 Subject: [PATCH 5/7] chore: update CODE_OF_CONDUCT.md file --- CODE_OF_CONDUCT.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 5a9533d3..f7137cad 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -57,9 +57,9 @@ further defined and clarified by project maintainers. This code of conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at -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, see -https://www.contributor-covenant.org/faq + From d563d812155ae47e77f5e17e50e70840960af7f7 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sun, 1 Feb 2026 05:41:03 +0100 Subject: [PATCH 6/7] chore: update CONTRIBUTING.md file --- CONTRIBUTING.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5d752a14..978d682a 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,5 +1,15 @@ # Contribute +Overall guidance on contributing to a PyAnsys library appears in the +[Contributing] topic in the *PyAnsys developer's guide*. Ensure that you +are thoroughly familiar with this guide before attempting to contribute to +PyConceptEV. + +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html + + +# Contribute + Overall guidance on contributing to a PyAnsys library appears in the [Contributing] topic in the *PyAnsys developer's guide*. Ensure that you are thoroughly familiar with this guide before attempting to contribute to @@ -9,4 +19,4 @@ The following contribution information is specific to {project-name}. [Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html - + \ No newline at end of file From bea96f9a3f75cd885bc853e7398b046f3ecfa0a2 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sun, 1 Feb 2026 05:41:06 +0100 Subject: [PATCH 7/7] chore: update LICENSE file --- LICENSE | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/LICENSE b/LICENSE index 3c96ad89..8a4a9b1a 100644 --- a/LICENSE +++ b/LICENSE @@ -1,6 +1,6 @@ MIT License -Copyright (c) 2023 - 2025 ANSYS, Inc. and/or its affiliates. +Copyright (c) 2023 - 2026 ANSYS, Inc. and/or its affiliates. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in @@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE -SOFTWARE. +SOFTWARE. \ No newline at end of file