feat: Conduit 0.14.0 release (#296)

* start 0.14.0 release

* doc: Record size limit on standalone connectors (#286)

* wip

* add reference to standalone connectors

* update changelog

* not the case

* update docs for `pipelines init` (#318)

* update

* update docs

* `split` and `clone` processor docs (#293)

* add split processor docs

* make diff a bit nicer (still not nice)

* fix empty line background

* add clone processor specs, update all processor specs, generate docs

* update clone specs

* add info about release

* increment announcement bar id

---------

Co-authored-by: Lovro Mažgon <[email protected]>

Author: raulb

changelog/2025-06-13-conduit-0-14-0-release.mdx

@@ -0,0 +1,23 @@
+---
+slug: '2025-06-13-conduit-0-14-0-release'
+title: Conduit v0.14.0 release
+draft: false
+tags: [conduit, release, conduit-release]
+---
+
+We're happy to announce the release of Conduit [v0.14.0](https://github.com/ConduitIO/conduit/releases/tag/v0.14.0), introducing the [`split`](/docs/using/processors/builtin/split) and [`clone`](/docs/using/processors/builtin/clone) processors, which enables one source record to trigger a write of multiple records in the destination.
+
+:::tip
+The new processors return multiple records, which is currently only supported in the new v2 engine. If you want to try them out, you need to start Conduit using `conduit run --preview.pipeline-arch-v2`.
+:::
+
+<!--truncate-->
+
+### Key Highlights
+
+- New option `--connectors.max-receive-record-size` in `conduit run` to configure the record size when using standalone connectors. [More information](/docs/using/connectors/installing#record-size-limitations).
+- Processor [`split`](/docs/using/processors/builtin/split) enables you to split an array in a record into separate records. This can be useful in AI pipelines where the input record contains a document and the output is multiple embeddings inserted into a database.
+- Processor [`clone`](/docs/using/processors/builtin/clone) enables you to clone any record N times. This is useful when one input record needs to be split into multiple collections (tables) on the destination.
+- Improvements for `pipelines init` command, which now creates a runnable demo pipeline when no flags are supplied.
+
+![scarf pixel conduit-site-changelog](https://static.scarf.sh/a.png?x-pxid=b43cda70-9a98-4938-8857-471cc05e99c5)

docs/0-what-is/1-getting-started.mdx

@@ -57,27 +57,30 @@ install any additional connector nor to change Conduit's default configuration.
 
 ## Build a pipeline
 
-Next, we can use the Conduit CLI to build the example pipeline:
+Next, we can use the Conduit CLI to build a demo pipeline:
 
 ```shell
 $ conduit pipelines init
 ```
 
-`conduit pipelines init` builds an example that generates flight information
-from an imaginary airport every second. Use `conduit pipelines init --help` to
-learn how to customize the pipeline.
+`conduit pipelines init` builds a demo pipeline that generates flight information
+from an imaginary airport every second.
 
 If the `pipelines` directory, you'll notice a new file,
-`pipeline-generator-to-file.yaml` that contains our pipeline's configuration:
+`demo-pipeline.yaml` that contains our pipeline's configuration:
 
 ```yaml
 version: "2.2"
 pipelines:
-  - id: example-pipeline
+  - id: "demo-pipeline"
+    description: "This pipeline was initialized using the `conduit pipelines init` command.
+It is a demo pipeline that connects a source connector (generator) to a destination connector (log).
+The next step is to simply run `conduit run` in your terminal and you should see a new record being logged every second.
+Check out https://conduit.io/docs/using/pipelines/configuration-file to learn about how this file is structured."
     status: running
-    name: "generator-to-file"
+    name: "demo-pipeline"
     connectors:
-      - id: example-source
+      - id: "generator-source"
         type: source
         plugin: "generator"
         settings:
@@ -98,31 +101,25 @@ pipelines:
           # Type: float
           # Optional
           rate: '1'
-      - id: example-destination
+      - id: "log-destination"
         type: destination
-        plugin: "file"
-        settings:
-          # Path is the file path used by the connector to read/write records.
-          # Type: string
-          # Optional
-          path: './destination.txt'
+        plugin: "log"
 ```
 
 The configuration above tells us some basic information about the pipeline (ID
 and name) and that we want Conduit to start the pipeline automatically (
 `status: running`).
 
 Then we see a source connector, that uses the [
-`generator` plugin](https://github.com/ConduitIO/conduit-connector-generator),
+`generator` plugin](/docs/using/connectors/list/generator),
 which is a built-in plugin that can generate random data. The source connector's
 settings translate into: generate structured data, 1 record per second. Each
 generated record should contain an `airline` field (type: string) and a
 `scheduledDeparture` field (type: duration).
 
 What follows is a destination connector where the data will be written to. It
-uses the `file` plugin, which is a built-in plugin that writes all the incoming
-data to a file. It has only one configuration parameter, which is the path to
-the file where the records will be written.
+uses the [`log` plugin](/docs/using/connectors/list/log), which is a built-in plugin that writes all the incoming
+data to a log you can see when you run Conduit.
 
 ## Run Conduit
 
@@ -132,32 +129,34 @@ With the pipeline configuration being ready, we can run Conduit:
 $ conduit run
 ```
 
-Conduit is now running the pipeline. Let's check the contents of the `destination.txt` using:
+Once Conduit starts running the pipeline, every second, you should see a log entry like this:
 
 ```shell
-tail -f destination.txt | jq
+2025-06-11T12:37:28+00:00 INF component=plugin.standalone connector_id=example-pipeline:example-destination plugin_name=conduit-connector-log record={"key":"aHlkYXRvcG5ldW1hdG9seXRpYw==","metadata":{"conduit.source.connector.id":"example-pipeline:example-source","opencdc.createdAt":"1749638247540840000","opencdc.payload.schema.subject":"example-pipeline:example-source:payload","opencdc.payload.schema.version":"1","opencdc.readAt":"1749638248541754000"},"operation":"create","payload":{"after":{"airline":"elytrorrhagia","scheduledDeparture":"2025-06-11T10:37:27.540841Z"},"before":null},"position":"Mg=="}
 ```
 
-Every second, you should see a JSON object like this:
+This log entry is Conduit's way of showing you the data that was generated by the generator connector. If we look into the `record` field, we can see the following JSON object:
 
-```shell
+
+```json
 {
-  "position": "MjU=",
-  "operation": "create",
+  "key": "aHlkYXRvcG5ldW1hdG9seXRpYw==",
   "metadata": {
     "conduit.source.connector.id": "example-pipeline:example-source",
-    "opencdc.createdAt": "1730801194148460912",
+    "opencdc.createdAt": "1749638247540840000",
     "opencdc.payload.schema.subject": "example-pipeline:example-source:payload",
-    "opencdc.payload.schema.version": "1"
+    "opencdc.payload.schema.version": "1",
+    "opencdc.readAt": "1749638248541754000"
   },
-  "key": "cHJlY2VwdG9yYWw=",
+  "operation": "create",
   "payload": {
-    "before": null,
     "after": {
-      "airline": "wheelmaker",
-      "scheduledDeparture": "2024-11-05T10:06:34.148469Z"
-    }
-  }
+      "airline": "elytrorrhagia",
+      "scheduledDeparture": "2025-06-11T10:37:27.540841Z"
+    },
+    "before": null
+  },
+  "position": "Mg=="
 }
 ```
 
@@ -168,18 +167,25 @@ holds the data being streamed as well as other data and metadata. In the
 
 ```json
 {
-    "airline": "wheelmaker",
-    "scheduledDeparture": "2024-11-05T10:06:34.148469Z"
+  "airline": "elytrorrhagia",
+  "scheduledDeparture": "2025-06-11T10:37:27.540841Z"
 }
 ```
 
 The pipeline will keep streaming the data from the generator source connector to
-the file destination connector as long as Conduit is running. To stop Conduit,
+the log destination connector as long as Conduit is running. To stop Conduit,
 press `Ctrl + C` (on a Linux OS, or the equivalent on other operating systems). This will
 trigger a graceful shutdown that stops reads from source connectors and waits
 for records that are still in the pipeline to be acknowledged. The next time
 Conduit starts, it will start reading data from where it stopped.
 
+
+:::tip
+Run `conduit pipelines init --help` to see how you can customize the pipeline
+configuration file that's being generated.
+:::
+
+
 ## What's next?
 
 Now that you've got the basics of running Conduit and creating a pipeline

docs/1-using/0-installing-and-running.mdx

@@ -63,12 +63,12 @@ First, download
 the [latest Conduit release](https://github.com/ConduitIO/conduit/releases/latest)
 for your platform.
 
-Let's say you downloaded `conduit_0.13.6_Windows_x86_64.zip`.
+Let's say you downloaded `conduit_0.14.0_Windows_x86_64.zip`.
 
 ### Unzip the archive
 
 ```shell
-tar -xf conduit_0.13.6_Windows_x86_64.zip
+tar -xf conduit_0.14.0_Windows_x86_64.zip
 ```
 
 ### Run
@@ -122,7 +122,7 @@ Before you can build Conduit from source, you need to have the latest version of
 1. Start by downloading the source code from the latest stable release on the Conduit [Releases Page](https://github.com/ConduitIO/conduit/releases/latest). Alternatively, you can run this command to automatically download the latest stable source to your current directory:
 
 ```shell
-$ TAG=v0.13.6; curl -o conduit.tar.gz -L https://github.com/ConduitIO/conduit/archive/refs/tags/$TAG.tar.gz
+$ TAG=v0.14.0; curl -o conduit.tar.gz -L https://github.com/ConduitIO/conduit/archive/refs/tags/$TAG.tar.gz
 ```
 
 A file called `conduit.tgz` will be in your current directory. The next step is to expand the source:
@@ -136,7 +136,7 @@ name might be different between releases since it's tied to the latest git sha
 for the commit.
 
 ```shell
-$ cd conduit-0.13.6
+$ cd conduit-0.14.0
 ```
 
 Now build the project:
@@ -166,7 +166,7 @@ on port 8080:
  `::::::::          ::::::::‘
       `::::        ::::‘
        `:::::....:::::‘
-         `::::::::::‘        Conduit v0.13.6 linux/amd64
+         `::::::::::‘        Conduit v0.14.0 linux/amd64
              ‘‘‘‘
 2025-01-10T09:40:07+00:00 INF All 0 tables opened in 0s component=badger.DB
 2025-01-10T09:40:07+00:00 INF Discard stats nextEmptySlot: 0 component=badger.DB