> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/introduction/release-info.md).

# Release info

{% hint style="info" %}
***This page must be considered part of the iSHARE Framework***

*This page is considered normative and is therefore compliant with RFC 2119.*
{% endhint %}

## Version 3.0.1

Version 3.0.1 updates the Developer Portal for the iSHARE v3.0 specifications. It includes the v3 role and claim models, the Participant Registry API material, revised delegation and credential guidance, and clarifications and corrections to the normative documentation.

The normative API definitions are published in the [iSHARE OpenAPI specifications](https://openapi.ishare.eu/?version=3.0). The Developer Portal provides the accompanying implementation guidance and examples.

## Historical releases

### Version 2.0.1

Version 2.0.1 introduced a new publication engine, role getting-started pages, formal-framework notices, a revised introduction, and the [single-party endpoint](/participant-registry-role/single-party.md).

### Version 2.0

Version 2.0 introduced the Satellite role (now Participant Registry) for participant administration and the Data Spaces concept. The changes included the `roles` attribute replacing `certifications` in `/parties`, the `/dataspaces` endpoint, and the `/ep_creation` endpoint for creating an Entitled Party.

For migration, implementations should use the current API specifications, support the current `/parties` representation, and follow the current [M2M authentication guidance](/reference/authentication.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.ishare.eu/introduction/release-info.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.