Merge branch 'main' into maint/ubuntu_latest

MaxJPRey · web-flow · commit cacd8a9a0d06 · 2025-11-10T11:37:34.000+01:00
diff --git a/.github/workflows/ci_cd.yml b/.github/workflows/ci_cd.yml
@@ -63,7 +63,7 @@ jobs:
     steps:
   
       - name: "Download HTML documentation artifacts"
-        uses: actions/download-artifact@v5
+        uses: actions/download-artifact@v6
         with:
           name: documentation-html
           path: documentation-html
@@ -84,7 +84,7 @@ jobs:
     steps:
 
     - name: "Download HTML documentation"
-      uses: actions/download-artifact@v5
+      uses: actions/download-artifact@v6
       with:
         name: documentation-html
         path: documentation-html
@@ -96,7 +96,7 @@ jobs:
         dest: documentation-html.zip
 
     - name: "Download PDF documentation"
-      uses: actions/download-artifact@v5
+      uses: actions/download-artifact@v6
       with:
         name: documentation-pdf
         path: documentation-pdf
@@ -125,7 +125,7 @@ jobs:
     steps:
   
       - name: "Download HTML documentation artifacts"
-        uses: actions/download-artifact@v5
+        uses: actions/download-artifact@v6
         with:
           name: documentation-html
           path: documentation-html
diff --git a/.github/workflows/nightly-build.yml b/.github/workflows/nightly-build.yml
@@ -45,14 +45,14 @@ jobs:
           make -C doc pdf
 
       - name: Upload HTML documentation
-        uses: actions/upload-artifact@v4.6.2
+        uses: actions/upload-artifact@v5.0.0
         with:
           name: HTML-Documentation
           path: doc/_build/html
           retention-days: 7
 
       - name: Upload PDF Documentation
-        uses: actions/upload-artifact@v4.6.2
+        uses: actions/upload-artifact@v5.0.0
         with:
           name: PDF-Documentation
           path: doc/_build/latex/pyansys*.pdf
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -2,7 +2,7 @@ repos:
 
 
 - repo: https://github.com/astral-sh/ruff-pre-commit
-  rev: v0.13.1
+  rev: v0.14.3
   hooks:
     - id: ruff-check
     - id: ruff-format
@@ -26,7 +26,7 @@ repos:
   - id: debug-statements
 
 - repo: https://github.com/python-jsonschema/check-jsonschema
-  rev: 0.34.0
+  rev: 0.34.1
   hooks:
     - id: check-github-workflows
       name: "Check GitHub workflows"
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
@@ -0,0 +1,65 @@
+# Contributor covenant code of conduct
+
+## Pledge
+
+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.
+
+## Standards
+
+Examples of behavior that contribute to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual
+  attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+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 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],
+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
@@ -1,14 +1,12 @@
-# Contributing
+# Contribute
 
-We absolutely welcome any code contributions and we hope that this
-guide will facilitate an understanding of the PyAnsys-dev-guide code
-repository. It is important to note that while the PyAnsys-dev-guide 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
+{project-name}.
 
-For further information about contributing to PyAnsys projects,
-refer to the [PyAnsys Developer's Guide](https://dev.docs.pyansys.com/).
+The following contribution information is specific to the PyAnsys Developer's Guide.
 
+[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html
+
+<!-- Begin content specific to your library here. -->
diff --git a/doc/source/how-to/releasing.rst b/doc/source/how-to/releasing.rst
@@ -95,6 +95,13 @@ control system.
     | |uncheck| All documentation builds successfully.
     | |uncheck| The project builds successfully.
 
+.. note:: Pre-releases
+
+   To perform a pre-release, the process is the same as described below, with the exception
+   of using a pre-release tag that follows `PEP 440 <https://peps.python.org/pep-0440/>`_.
+   Furthermore, limiting pre-release tags to ``N.N.N[{a|b|rc}N]`` subset is encouraged for
+   PyAnsys libraries.
+
 .. dropdown:: Release major and minor versions
 
     Before performing a release, you must verify that your ``origin main`` branch is up to date
diff --git a/doc/source/how-to/vulnerabilities.rst b/doc/source/how-to/vulnerabilities.rst
@@ -622,7 +622,7 @@ Fixing it is important because malicious inputs could execute unintended command
             run: |
               echo ${{ github.workspace }} # Template expansions are resolved before workflows and jobs run. These expansions
               echo ${{ runner.temp }} # insert their results directly into the context, which can accidentally introduce shell injection risks.
-              echo ${{ input.user-input }} # This is especially through when such expansion is from a user input.
+              echo ${{ input.user-input }} # This is especially true when such expansion is from a user input.
 
 
   .. tab-item:: Remediation
diff --git a/doc/source/packaging/diag/grpc_structure_diag.rst b/doc/source/packaging/diag/grpc_structure_diag.rst
@@ -19,6 +19,10 @@
            label="ansys-api-product", shape="folder"
          ];
 
+         src [
+           label="src", shape="folder"
+         ];
+
          ansys [
            label="ansys", shape="folder"
          ];
@@ -44,7 +48,8 @@
          ];
 
 
-         ansys_api_product -> ansys;
+         ansys_api_product -> src;
+         src -> ansys;
          ansys -> api;
          api -> product;
          product -> version;
diff --git a/doc/source/packaging/structure.rst b/doc/source/packaging/structure.rst
@@ -307,6 +307,9 @@ for build-system backend tools commonly used in the Python ecosystem:
 
 .. include:: code/pyproject_code.rst
 
+Optional files
+==============
+
 The ``setup.py`` file
 ---------------------
 
diff --git a/requirements/requirements_doc.txt b/requirements/requirements_doc.txt
@@ -1,9 +1,9 @@
 Sphinx==8.2.3
-ansys-sphinx-theme==1.6.1
+ansys-sphinx-theme==1.6.3
 sphinx-copybutton==0.5.2
 sphinx_toolbox==4.0.0
 sphinx_design==0.6.1
 sphinxcontrib-mermaid>=0.7.1
 sphinx-gallery==0.19.0
 Pillow>=9.0
-pyvista==0.46.3
+pyvista==0.46.4
