> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/truvera-workspace/truvera-workspace-release-notes/2025-release-notes/release-notes-q2-2025.md). # Release notes Q2 2025 ## v1.63.0 June 14 ### Updates and new features DCKA-4847 Separated job processing into its own service ## v1.62.0 May 14 ### Bug fixes DCKA-4841 Fix verification history showing each verifier 3 times DCKA-4842 Fix an issued with creating did:cheqd on testnet ## v1.61.0 April 14 ### Updates and new features DCKA-3819 Support for EDV labels entries based on the application that creates it DCKA-4834 Convert API to ESM modules DCKA-4836 Upgrade gcsRDSBackup and API to newer node version DCKA-4927 Create wallet-edv-storage package ### Bug fixes DCKA-4816 Fix subaccount billing DCKA-4821 Fix credential table resizing bug ## v1.60.0 April 3 ### Updates and new features DCKA-4779 Upon issuance of the credential there will be no download of the issued credential, credential needs to be distributed via email or DID during issuance or if persisted can be downloaded from the credential view. DCKA-4802 Update API OID4VCI flows to support latest spec requirements ### Bug fixes DCKA-3089 Fixed an error where the verification template attribute field would change value if edited. --- # 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.truvera.io/truvera-workspace/truvera-workspace-release-notes/2025-release-notes/release-notes-q2-2025.md?ask=&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.