> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/devolutions-password-manager-life-cycle-policies/devolutions-password-manager-macos-life-cycle-policy.md).

# Política de ciclo de vida de Devolutions Password Manager macOS

La política de ciclo de vida de Devolutions Password Manager para macOS cubre las tres versiones principales más recientes de macOS, incluida la actual.

Devolutions garantizará la compatibilidad de Devolutions Password Manager con la versión actual de macOS y con las tres versiones principales más recientes, incluida la actual (p. ej., desde macOS 14 hasta macOS 12).

Una «versión principal» se define como un lanzamiento oficial y numerado que incluye cambios, mejoras o actualizaciones significativas (p. ej., de macOS 13 a macOS 14). Es responsabilidad del usuario asegurarse de que su dispositivo funcione con una versión de macOS compatible con Devolutions Password Manager.

La compatibilidad con versiones anteriores de macOS no está garantizada y puede provocar una funcionalidad reducida o la imposibilidad de uso. Devolutions no será responsable de ningún fallo, imposibilidad de funcionamiento o problema de rendimiento de Devolutions Password Manager derivado de su uso en versiones de macOS no compatibles u obsoletas, y se reserva el derecho, a su entera discreción, de determinar la fecha de finalización del soporte para versiones anteriores de macOS.


---

# 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 dynamically by asking a question.

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

```
GET https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/devolutions-password-manager-life-cycle-policies/devolutions-password-manager-macos-life-cycle-policy.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 `build a script that syncs our docs to a CMS` 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.