> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-01-129.md).

# 34.01.129 (Build 34.01.129)

The following table has the release details:

| Build        | 34.01.129                                                        |
| ------------ | ---------------------------------------------------------------- |
| Code name    | Quinn Update 1                                                   |
| Release date | June 11, 2025                                                    |
| Type         | Maintenance release                                              |
| SHA-256      | c9dd890a734843b60a9da249d10844d805bad53cb58ca1708c017a1307c6ccc6 |

This 34.01.129 build is a maintenance release for Quinn Update 1 (34.01). The upgrade paths applicable to build 34.01.126 apply to this build as well.

Review the [34.01 (build number 126) release notes](https://docs.prismacloud.io/en/compute-edition/34/rn/release-information/release-notes-34-01) for the upgrade paths and other details on the Quinn Update 1 release.

Review the [system requirements](https://docs.prismacloud.io/en/compute-edition/34/admin-guide/install/system-requirements) to learn about the supported operating systems, hypervisors, runtimes, tools, and orchestrators.

## Addressed Issues

* This maintenance release addresses an internal session management issue.


---

# 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.prismacloud.io/ce-release-notes/prisma-tm-cloud-compute-edition-release-information/release-notes-34-01-129.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.
