> 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-certify/releases/version-0.10.2.md).

# Version 0.10.2

**Release Version**: v0.10.2 (Patch)

**Release Type**: Developer Release

**Release** **Date**: 21st Feb, 2025

## **Overview**

This patch release **0.10.2** for **Inji Certify** addresses fixes related to release versions, ensuring that the correct images of **Inji Web** and **Mimoto** are selected during local deployment using **Docker Compose**.

## **Bug Fixes**

Below is the list of bug fixes as part of the **0.10.2** release:

| **Jira ID**                                                     | **Description**                                                     |
| --------------------------------------------------------------- | ------------------------------------------------------------------- |
| [INJICERT-926](https://mosip.atlassian.net/browse/INJICERT-926) | Unable to pull image of Inji web and mimoto during local deployment |

## **Repository Released**

| **Repositories**           | **Tags Released**                                                                   |
| -------------------------- | ----------------------------------------------------------------------------------- |
| inji-certify               | [**v0.10.2**](https://github.com/mosip/inji-certify/tree/v0.10.2)                   |
| digital-credential-plugins | [**v0.10.0**](https://github.com/mosip/esignet-mock-services/tree/v0.10.0)          |
| artifactory                | [**v0.10.0-INJI**](https://github.com/mosip/digital-credential-plugins/tree/v0.3.0) |
| inji-config                | [**v0.5.0**](https://github.com/mosip/inji-config/tree/v0.5.0)                      |
| keymanager                 | [**v1.3.0-beta.2**](https://github.com/mosip/keymanager/tree/v1.3.0-beta.2)         |

## **Compatible Modules**

The following table outlines the tested and certified compatibility of \<release version> with other modules.

| **Module**           | **Version(With tag links)**                                                         |
| -------------------- | ----------------------------------------------------------------------------------- |
| eSignet              | [**v1.4.1**](https://github.com/mosip/esignet/tree/v1.4.1)                          |
| Sunbird C            | [**v2.0.0**](https://github.com/Sunbird-RC/sunbird-rc-core/releases/tag/v2.0.0-rc3) |
| Key Manager          | [**v1.3.0-beta.2**](https://github.com/mosip/keymanager/tree/v1.3.0-beta.2)         |
| commons              | [**v1.3.0-beta.1**](https://github.com/mosip/commons/tree/v1.3.0-beta.1)            |
| mock-identity-system | [**v0.10.0**](https://github.com/mosip/esignet-mock-services/tree/v0.10.0)          |

## Documentation:

* [QA Report](https://docs.inji.io/inji-certify/releases/version-0.10.2/test-report)


---

# 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-certify/releases/version-0.10.2.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.