> For the complete documentation index, see [llms.txt](https://docs.inji.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inji.io/inji-verify/releases/version-0.13.1.md).

# Version 0.13.1

**Release Name**: Inji Verify v0.13.1

**Support**: Developer Release

**Release Date**: 20th Aug, 2025

### Overview

The Inji Verify 0.13.1 patch release includes critical fixes to ensure smooth deployment and prevent issues encountered in version 0.13.0.

### Key Updates:

**1. Database Upgrade Script Fix:**

* In version 0.13.0, the db\_upgrade script was missing the table creation script `verify-vc_submission.sql`.This caused the Inji Verify service to fail when upgrading from version 0.12.3 (which already had the database set up), as the required table was not created.
* The previous workaround (in 0.13.0) required manually running `verify-vc_submission.sql` from db\_scripts.
* **Fix**: This patch release now includes the missing script in db\_scripts, ensuring the table is created automatically during upgrades.

{% hint style="warning" %}
**Note:** We recommend upgrading directly to Inji Verify v0.13.1 instead of using v0.13.0. If you continue using v0.13.0, you must manually run verify-vc\_submission.sql from db\_scripts to create the required table.
{% endhint %}

### Repositories: Released/Dependent

| Repositories | Tags: Released/Dependent                                     |
| ------------ | ------------------------------------------------------------ |
| Inji Verify  | [v0.13.1](https://github.com/mosip/inji-verify/tree/v0.13.1) |

### Projects: Released

Inji Verify Repositories: 4 projects (all these projects are of same version) as below:

1. inji-verify-service - [0.13.1 Inji Verify service](https://github.com/mosip/inji-verify/tree/release-0.13.x/verify-service)
2. inji-verify-ui (ref implementation) - <https://github.com/mosip/inji-verify/tree/release-0.13.x/verify-ui>
3. SDK - <https://github.com/mosip/inji-verify/tree/release-0.13.x/inji-verify-sdk>
4. API-Test - <https://github.com/mosip/inji-verify/tree/release-0.13.x/api-test>

### Compatible modules

The following table outlines the tested and certified compatibility of Inji Verify 0.13.1 with other modules.

<table><thead><tr><th width="228.04827880859375">Module</th><th>Version</th></tr></thead><tbody><tr><td>Inji Mobile Wallet</td><td><a href="https://github.com/mosip/inji-wallet/tree/v0.17.0">0.17.0</a></td></tr><tr><td>Inji Web Wallet</td><td><a href="https://github.com/mosip/inji-web/tree/v0.12.0">0.12.0</a></td></tr><tr><td>Pixel-Pass library</td><td><a href="https://github.com/mosip/pixelpass/tree/v0.6.0">v0.6.0</a></td></tr><tr><td>vc-verifier library</td><td><a href="https://github.com/mosip/vc-verifier/tree/v1.3.0">v1.3.0</a></td></tr></tbody></table>

### Release Scope

Please refer to the list of items covered as part of [0.13.1](https://mosip.atlassian.net/issues/?filter=11694\&jql=project%20%3D%20%22Inji%20Verify%22%20AND%20issuetype%20in%20%28Story%2C%20Task%2C%20Bug%29%20and%20fixversion%3D0.13.1) patch release.

### Bug Fixes

Below is the list of fixes as part of the 0.13.1 release:

<table><thead><tr><th width="222.41973876953125">Jira ID</th><th>Description</th></tr></thead><tbody><tr><td><a href="https://mosip.atlassian.net/browse/INJIVER-1255">INJIVER-1255</a></td><td>The db_upgrade script for version 0.13.0 is missing the table creation script <code>verify-vc_submission.sql</code>. As a result, when upgrading from version 0.12.3 (which already had the database setup), the required table was not created, causing the inji-verify service to fail.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/INJIVER-1271">INJIVER-1271</a></td><td>VP Verification was failing for MOSIP National ID VC as there was a case-sensitive mismatch in “type” of config.json.</td></tr><tr><td><a href="https://mosip.atlassian.net/browse/INJIVER-1251">INJIVER-1251</a></td><td>API automation failure observed for the /vp-result endpoint with 0.13.0 images in the released environment.</td></tr></tbody></table>

### Documentation

* [Feature documentation](https://github.com/mosip/documentation/blob/inji/docs/overview/features.md)
* [Integration Guide](https://github.com/mosip/documentation/blob/inji/inji-wallet/inji-mobile/technical-overview/integration-guide/openid4vp.md)
* [API Documentation](https://mosip.stoplight.io/studio/inji-verify)
* [Collab Guide](https://github.com/mosip/documentation/blob/inji/docs/functional-overview/releases-1/inji-verify-collab-guide.md)
* [QA Report](/inji-verify/releases/version-0.13.1/test-report.md)


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.inji.io/inji-verify/releases/version-0.13.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.