diff --git a/.github/workflows/ci_cd.yml b/.github/workflows/ci_cd.yml index b2756f7..ba6499a 100644 --- a/.github/workflows/ci_cd.yml +++ b/.github/workflows/ci_cd.yml @@ -68,7 +68,7 @@ jobs: strategy: matrix: os: [windows-latest] - scade-version: ['24.2'] + scade-version: ['25.2'] fail-fast: false steps: - name: "Install Git and clone project" diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index b4bcbe5..f7137ca 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, socioeconomic 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,18 +48,18 @@ 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 + [homepage]: https://www.contributor-covenant.org For answers to common questions about this code of conduct, see -https://www.contributor-covenant.org/faq + diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 9aeb300..e14d5b1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,14 +1,12 @@ -# Contributing +# Contribute -We absolutely welcome any code contributions and we hope that this -guide will facilitate an understanding of the Ansys SCADE Python Wrapper code -repository. It is important to note that while the Ansys SCADE Python Wrapper software -package is maintained by ANSYS and any submissions will be reviewed -thoroughly before merging, we still seek to foster a community that can -support user questions and develop new features to make this software -a useful tool for all users. 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 +Ansys SCADE Python Wrapper. -For contributing to this project, please refer to the [PyAnsys Developer's Guide]. +The following contribution information is specific to Ansys SCADE Python Wrapper. -[PyAnsys Developer's Guide]: https://dev.docs.pyansys.com/index.html +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html + + diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 0000000..5a88c01 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,16 @@ +# Security Policy + +## Reporting a vulnerability + +> [!CAUTION] +> Do not use GitHub issues to report any security vulnerabilities. + +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. + +Provide the PyAnsys Core team with this information: + +- 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 diff --git a/doc/changelog.d/51.miscellaneous.md b/doc/changelog.d/51.miscellaneous.md new file mode 100644 index 0000000..64e808b --- /dev/null +++ b/doc/changelog.d/51.miscellaneous.md @@ -0,0 +1 @@ +Chore: Update missing or outdated files