Logan Adams

This commit performs a **maintenance chore** by **updating the project's version number** to `0.18.10`. Specifically, it modifies the `version.txt` file, which is a core component of the **project versioning system**. This ensures that all subsequent builds and releases accurately report the current software iteration, providing correct identification for users and automated systems. The change from `0.18.9` to `0.18.10` reflects a minor update or patch release.

This commit performs a **maintenance chore** by updating the project's version number in preparation for an upcoming release. It specifically changes the version from `0.18.8` to `0.18.9` within the `version.txt` file. This update signals the readiness for the **0.18.9 release**, ensuring that all build and packaging processes correctly reflect the new version identifier. The change primarily impacts the **project versioning** and release management, with no functional code changes.

This commit performs a **maintenance chore** by updating the project's version number, incrementing it from `0.18.7` to `0.18.8`. This change is reflected in the `version.txt` file, which is central to the **project's release identification**. It signifies a progression in the development cycle, typically preceding a new release or marking a new development iteration.

This commit performs **post-release maintenance** by **updating the project's version number** from `0.18.6` to `0.18.7` within the `version.txt` file. This change signals a new **patch release** of the **DeepSpeed library**, indicating minor fixes or improvements since the previous version. It ensures that all subsequent builds and distributions will correctly reflect the updated software version, impacting how users identify the current release.

This commit **updates the project's official version number** recorded in the `version.txt` file from `0.18.5` to `0.18.6`. This is a **maintenance chore** performed as part of the release process to ensure the project's reported version is accurate. It directly affects the **project versioning system** and is crucial for correct identification in build artifacts, package metadata, and user-facing information.

This commit performs a **documentation update** to reflect a significant change in the project's contribution policy. It **removes references to the outdated Microsoft CLA** and instead directs contributors to the Developer Certificate of Origin (DCO). Specifically, the **contributing documentation** in `README.md`, `docs/contributing.md`, and `docs/index.md` has been updated to guide users towards the DCO process. This **maintenance** effort ensures that all contribution guidelines are current and simplifies the legal requirements for new contributors.

This commit performs **maintenance cleanup** by **removing cron and pull request triggers** associated with **outdated V100 tests** from the **CI/CD pipeline**. Although the V100 test jobs were already disabled, their triggers were still causing unnecessary CI cron jobs to be initiated. This change prevents these redundant job initiations, streamlining the **CI infrastructure** and preparing for the subsequent removal of the obsolete YAML configuration files.

This commit **updates the project's `README.md`** to reflect the latest **Continuous Integration (CI) status badges**. It replaces outdated badge links with newer, more accurate ones, ensuring that the reported build health and test results are always current. This is a **documentation maintenance** task that improves the **project's public-facing status reporting**, providing clearer and more reliable information to users and contributors about the current state of the codebase.

This commit performs a **maintenance chore** by updating the **project version** within the `version.txt` file. Specifically, it increments the version number from `0.18.4` to `0.18.5`. This change is a standard part of the **release management process**, indicating the project's progression to the next development iteration following the `0.18.4` release.

This commit **updates the continuous integration (CI) pipeline** to **enable testing and validation** against **Python 3.11 and 3.12**. It modifies the `.github/workflows/python.yml` file, which is the **Python CI workflow**, to include these new versions in the test matrix. This **maintenance and infrastructure update** ensures the project's compatibility with newer Python environments. The changes involve adjusting the base image and adding necessary steps for installing build dependencies and PyTorch, thereby **validating stability** for users on these versions.

This commit **updates the project's security policy documentation** by modifying the `SECURITY.md` file. The primary change redirects the official channel for **vulnerability reporting from Microsoft to GitHub**, leveraging GitHub's native security features for a more integrated process. This **documentation update** also includes revisions to the issue triage process, threat model, and severity categories, enhancing the clarity and effectiveness of the project's security response. The change streamlines how external parties report security concerns, improving the overall **security posture and incident management** for the project.

This commit performs a **routine maintenance chore** by **updating the project's version identifier** within the `version.txt` file. Specifically, the version number has been incremented from `0.18.2` to `0.18.3`, reflecting a new official release. This change primarily affects the **project's versioning metadata** and ensures that all build processes and user-facing information correctly report the current software iteration. It is a critical update for release management and downstream consumption of the software.

This commit performs a **maintenance chore** by updating the **project version** from `0.18.1` to `0.18.2` within the `version.txt` file. This change semantically marks the project's progression after the `0.18.1` release, preparing it for subsequent development or a new patch cycle. It primarily affects the **versioning metadata** and has no functional impact on the software's runtime behavior, serving purely as an administrative update.

This commit performs a **maintenance update** to the project's **versioning metadata**. It specifically increments the version number recorded in the `version.txt` file from `0.17.6` to `0.17.7`. This change reflects the project's progression to the next development cycle immediately following the `0.17.6` release. It ensures that any build systems, packaging tools, or user-facing displays relying on this file will report the correct, updated **project version**.

This commit performs a **routine maintenance chore** by updating the project's **version metadata**. Specifically, it increments the version number recorded in `version.txt` from `0.17.5` to `0.17.6`. This administrative change is essential for **accurate release identification** and reflects the project's current development state following the `0.17.5` release. It has no impact on application functionality or behavior, serving solely to keep the official version string up-to-date.

This commit performs a **maintenance** update to the project's **versioning system**. It specifically increments the version number within the `version.txt` file from `0.17.4` to `0.17.5`. This change reflects the completion of the `v0.17.4` release and prepares the codebase for ongoing development towards the next version. It ensures that any subsequent builds or deployments will correctly report the updated development version, maintaining accurate project metadata.

This commit **updates the project's internal version number** from `0.17.3` to `0.17.4` within the `version.txt` file. This is a **post-release maintenance chore** performed to prepare the codebase for subsequent development cycles following the `0.17.3` release. It primarily affects the **release metadata** and ensures that any build processes or tools relying on `version.txt` will reflect the correct, upcoming development version.

This commit performs **code cleanup** by **removing additional unused test files** specifically from the **`human-eval` module**. These tests were identified as obsolete, and their elimination streamlines the project's test suite. The change primarily impacts the **maintenance overhead** of the `human-eval` component, reducing unnecessary code and improving the clarity of the testing infrastructure.

This commit was intended to perform **documentation maintenance** by **removing outdated references to tests** from the project's `README.md` file. The objective was to update the documentation to accurately reflect the current state of the test suite, specifically targeting tests that have already been removed from the codebase. However, as **no file changes are recorded**, this commit effectively introduces no modifications to the project's documentation or any other module, making it an **empty commit**.

This commit performs a **maintenance chore** by updating the project's internal version number. Specifically, it increments the version from `0.17.2` to `0.17.3` within the `version.txt` file. This change is a standard part of the **release process**, preparing the repository for ongoing development after the `v0.17.2` release. It ensures that all subsequent builds and development snapshots will correctly reflect the upcoming version, impacting the **project versioning** metadata.