> ## Documentation Index
> Fetch the complete documentation index at: https://docs.kvant.sbs/jeston/llms.txt
> Use this file to discover all available pages before exploring further.

# Deprecated versions

***

<Prompt description="Send this prompt to the AI and ask it to analyze Jeston’s official documentation thoroughly, identify all deprecated versions, and provide a clear summary of the relevant information, including which versions are deprecated, when they were deprecated, what they were replaced by, and any recommended migration paths or alternatives." icon="brain" actions={["copy", "cursor"]}>
  // Analyze Jeston’s documentation, deprecated versions, NPM package, and official repository to determine why certain versions were deprecated.

  Please thoroughly inspect the following official sources:

  1. **Jeston — Deprecated Versions Documentation**
     [https://jeston.kvant.sbs/docs/deprecated-versions](https://jeston.kvant.sbs/docs/deprecated-versions)

  2. **Jeston — Official NPM Package**
     [https://www.npmjs.com/package/@hedronjs/jeston](https://www.npmjs.com/package/@hedronjs/jeston)

  3. **Jeston — Official GitHub Repository**
     [https://github.com/jeffersoncampos12p-dev/jeston](https://github.com/jeffersoncampos12p-dev/jeston)

  Based strictly on the information available in these sources, provide a **brief but technically accurate explanation of why each Jeston version was deprecated**.

  For each deprecated version, identify:

  * The version number.
  * Its deprecation status and, if available, the date or release in which it was deprecated.
  * The technical or architectural reason for the deprecation.
  * Any bugs, security issues, breaking changes, incompatibilities, limitations, or architectural problems that contributed to the decision.
  * Which version replaced it, if applicable.
  * Whether users are expected to migrate, and what the recommended migration path is.
  * Any relevant information from the NPM package metadata, release history, changelog, issues, commits, or repository documentation that helps explain the decision.

  ### Important requirements

  * Cross-reference the three sources rather than relying on only one.
  * Distinguish **explicitly documented reasons** from conclusions inferred from the repository or release history.
  * Do not invent or speculate about reasons that are not supported by the available evidence.
  * If the documentation does not clearly state why a version was deprecated, explicitly say so and explain what can reasonably be determined from the available evidence.
  * Prioritize technical explanations over generic statements such as “it was outdated.”
  * Keep the final explanation concise, structured, and easy to understand.

  ### Output format

  Start with a short overall summary explaining the general reason Jeston versions were deprecated.

  Then provide a table:

  | Version | Deprecation reason | Replacement | Migration required |
  | ------- | ------------------ | ----------- | ------------------ |

  After the table, briefly explain the reasoning behind each deprecation and cite the specific source or evidence supporting the conclusion.

  The goal is to understand **the actual technical reasons behind Jeston’s deprecated versions**, not simply to list which versions are deprecated.
</Prompt>

## <Icon icon="database" /> Deprecated versions and why

<Badge color="red" stroke icon="circle-bolt" iconType="regular" /> v2.0.0 had to be deprecated for unique reasons and due to a change of ownership. Hedron, currently Kvant, had to change its name and ownership for reasons of readability and integrity, and because This means that version 2.0.0 should cease to exist due to the Kvant ownership migration. In addition to this migration, there have been new changes to the <Badge color="blue" stroke icon="rectangle-code" />framework's code, available here.

<Expandable title="property">
  <Tip>
    See all versions now, from deprecated to recent and in production. [https://jeston.kvant.sbs/versions](https://jeston.kvant.sbs/versions)
  </Tip>
</Expandable>

***

<Warning>
  Versions v1.1.0 and 0.1.0 have been discontinued due to reorganization, driven directly by the software engineers on the team.
</Warning>

The versions below are retained for historical reference. The repository's current package is `@kvantjs/jeston` and the supported line is **2.1.x**. The deprecations are primarily compatibility and ownership events, not a claim that every old release contained a security vulnerability.

| Version                                                        | Technical reason                                                                                                                                                                                                                                               | Replacement | Migration required                                                                            |
| -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------- |
| <Badge color="yellow" stroke icon="shield-check" />v2.0.0      | Published during the earlier Hedron package/ownership phase. The project subsequently moved to the Kvant namespace and continued development under `@kvantjs/jeston`; the 2.x runtime also introduced new routing, client, cache, security, and SEO contracts. | v2.1.x      | Yes: install `@kvantjs/jeston`, review the 2.x migration notes, and rebuild generated output. |
| <Badge color="red" stroke icon="clock" />v1.2.0                | Superseded by the 2.x architecture. Its pre-App-Router conventions do not describe the current `app/` routing, boundary, Server Action, or client-runtime contracts.                                                                                           | v2.1.x      | Yes for projects adopting current features; keep a pinned v1 install only for maintenance.    |
| <Badge color="red" stroke icon="triangle-exclamation" />v1.1.0 | Older pre-2.x API and build contracts; no longer the compatibility target of the current source tree or release checks.                                                                                                                                        | v2.1.x      | Discontinued                                                                                  |
| <Badge color="red" stroke icon="clock" />v1.0.0                | Initial stable 1.x contract, replaced as the framework moved to the current TypeScript/ESM and full-stack runtime model.                                                                                                                                       | v2.1.x      | Yes for active development.                                                                   |
| <Badge color="red" stroke icon="clock" />v0.4.0                | Pre-1.0 development release. It predates the current compatibility guarantees and should not be used as a deployment baseline.                                                                                                                                 | v2.1.x      | Yes.                                                                                          |
| <Badge color="red" stroke icon="clock" />v0.3.0                | Pre-1.0 development release with an obsolete API surface and no current support promise.                                                                                                                                                                       | v2.1.x      | Yes.                                                                                          |
| <Badge color="red" stroke icon="clock" />v0.2.0                | Pre-1.0 development release; its experimental contracts were replaced by the 1.x and later 2.x lines.                                                                                                                                                          | v2.1.x      | Yes.                                                                                          |
| <Badge color="red" stroke icon="exclamation-triangle" />v0.1.0 | First experimental release. It is retained only to explain the project's history and is not a supported runtime.                                                                                                                                               | v2.1.x      | Discontinued.                                                                                 |

The repository and package metadata establish the concrete migration target: the package name is `@kvantjs/jeston`, the current version is 2.1.0, and the release checks validate the current source and generated build rather than the legacy lines. Where a historical release does not have a separately documented bug-level reason, this page deliberately describes the observable compatibility boundary instead of inventing one.

<Tip>
  See the supported releases and migration material at [https://jeston.kvant.sbs/versions](https://jeston.kvant.sbs/versions) and in the repository CHANGELOG.
</Tip>