}
    val newReleasedVersions = updateReleasedVersions(currentReleasedVersion, releasedVersions)
    releasedVersionsFile.writeText(GsonBuilder().setPrettyPrinting().create().toJson(newReleasedVersions))
}


fun updateReleasedVersions(currentReleasedVersion: ReleasedVersion, releasedVersions: ReleasedVersions) =
    ReleasedVersions(
        if (currentReleasedVersion.gradleVersion().isSnapshot) {

    /**
     * Retrieves all available dictionary files.
     *
     * @return JSON response containing list of dictionary files
     */
    // GET /api/admin/dict
    @Execute
    public JsonResponse<ApiResult> get$index() {
        final DictionaryFile<? extends DictionaryItem>[] dictFiles = dictionaryManager.getDictionaryFiles();
        return asJson(new ApiResult.ApiConfigsResponse<ListBody>()

```

Pode até ser um Stream infinito, em que você continua enviando dados.

## JSON Lines { #json-lines }

Nesses casos, é comum enviar "**JSON Lines**", um formato em que você envia um objeto JSON por linha.

Uma response teria um tipo de conteúdo `application/jsonl` (em vez de `application/json`) e o corpo seria algo como:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}

# JSON mit Bytes als base64 { #json-with-bytes-as-base64 }

Wenn Ihre App JSON-Daten empfangen und senden muss, Sie darin aber Binärdaten einschließen müssen, können Sie diese als base64 kodieren.

## Base64 vs Dateien { #base64-vs-files }

# JSON'da Bytes'i Base64 Olarak Kullanma { #json-with-bytes-as-base64 }

Uygulamanız JSON veri alıp gönderiyorsa ve bunun içine ikili (binary) veri eklemeniz gerekiyorsa, veriyi base64 olarak encode edebilirsiniz.

## Base64 ve Dosyalar { #base64-vs-files }

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$id": "https://github.com/elastic/elasticsearch/tree/master/docs/changelog",
  "$ref": "#/definitions/Changelog",
  "definitions": {
    "Changelog": {
      "type": "object",
      "properties": {
        "pr": {
          "type": "integer"
        },
        "issues": {
          "type": "array",
          "items": {
            "type": "integer"
          }
        },

* [`pydantic-extra-types`](https://docs.pydantic.dev/latest/usage/types/extra_types/extra_types/) - Pydantic で使用する追加の型のため。

追加のオプション FastAPI 依存関係:

* [`orjson`](https://github.com/ijl/orjson) - `ORJSONResponse` を使用したい場合に必要です。
* [`ujson`](https://github.com/esnme/ultrajson) - `UJSONResponse` を使用したい場合に必要です。

## ライセンス { #license }

## JSON Lines { #json-lines }

In diesen Fällen ist es üblich, „JSON Lines“ zu senden, das ist ein Format, bei dem Sie pro Zeile genau ein JSON-Objekt senden.

Eine Response hätte einen Content-Type von `application/jsonl` (anstelle von `application/json`) und der Body sähe etwa so aus:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}

    Note over App: Keeps producing...
    Note over Client: Keeps consuming...
```

它甚至可以是無限串流，你可以一直持續傳送資料。

## JSON Lines { #json-lines }

在這些情況下，常見做法是傳送「**JSON Lines**」，這是一種每一行各包含一個 JSON 物件的格式。

回應的 content type 會是 `application/jsonl`（而不是 `application/json`），而本體內容會像這樣：

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}
{"name": "Portal Gun", "description": "A portal opening device."}

```

Incluso podría ser un stream infinito, donde sigues enviando datos.

## JSON Lines { #json-lines }

En estos casos, es común enviar "**JSON Lines**", que es un formato donde envías un objeto JSON por línea.

Una response tendría un tipo de contenido `application/jsonl` (en lugar de `application/json`) y el response body sería algo como:

```json
{"name": "Plumbus", "description": "A multi-purpose household device."}