> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/release-notes/enterprise/keeper-secrets-manager/2024/july-2024.md).

# July 2024

## KSM HashiCorp Vault Plugin 1.0.3

* KSM-503: Added record delete operation
* KSM-504: Added ExistenceCheck with Validator
* KSM-505: Added UID as path parameter

## KSM PowerShell 16.6.6

* Bumping KSM .NET SDK version to 16.6.6

## KSM .NET SDK 16.6.6

* KSM-360: GHA to build and release strong named assemblies
* KSM-490: Switch some internal classes to public - for use in plugins
* KSM-515: Update to Bouncy Castle 2.4.0
* KSM-536: Update to System.Text.Json 8.0.4
* KSM-517: Add support for netstandard2.0 target
* KSM-542: Fix PowerShell module to allow dot in title

## KSM Python SDK 16.6.5

* KSM-529: Handle broken encryption in records and files

## KSM CLI 1.1.5

* Bumping KSM SDK to 16.6.5


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.keeper.io/release-notes/enterprise/keeper-secrets-manager/2024/july-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.