> For the complete documentation index, see [llms.txt](https://rc.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rc.sunbird.org/use/releases.md).

# Releases

## Latest release — v2.1.0

**Released 10 August 2026** · Tagged `v2.1.0`

v2.1.0 is the first feature-bearing release of Sunbird RC in roughly two years — the last was v2.0.2 in August 2024, with v2.0.3 a maintenance release in between. It is both a major feature release and a platform-wide upgrade: every service in the repository has been touched, either to add the new capability or to bring its runtime and dependency tree up to date.

The headline is **OpenID Connect for Verifiable Credentials**. A new `oid4vc-service` makes the platform speak OpenID4VCI 1.0 for issuance and OpenID4VP 1.0/draft-23 for presentation, so any conformant wallet can receive a credential from a Sunbird RC deployment and present it back to a Sunbird RC verifier — with no Sunbird-specific integration on the wallet side.

{% content-ref url="/pages/TES2EBXdlACN3ZRtcLpk" %}
[v2.1.0 — Latest release](/use/releases/credentialing/v2.1.0-latest-release.md)
{% endcontent-ref %}

{% hint style="info" %}
**Checkout other** <a href="https://github.com/orgs/Sunbird-RC/packages?repo_name=sunbird-rc-core" class="button primary small" data-icon="box-isometric">Releases & Changelogs</a>
{% endhint %}


---

# 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://rc.sunbird.org/use/releases.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.