Prepare repository for Tenzir v4.0.0-rc6 (#3328)

This commit is was created with /scripts/prepare-release.

Here is a high-level summary of the changes:

* Updated `/version.json` to v4.0.0-rc6 and the expected rev-count of
the merge commit to 17355.
* Generated a new entry in the docs version selector list.
* Removed the docs for the previous release candidate.
* Moved all changelog entries from `/changelog/next` to
`/changelog/v4.0.0-rc6`.
* Moved all changelog entries from `/changelog/v4.0.0-rc5` to
`/changelog/v4.0.0-rc6`.
* Updated the python bindings version in `/python/pyproject.toml` to
v4.0.0-rc6.

python/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "pyvast"
-version = "4.0.0-rc5"
+version = "4.0.0-rc6"
 description = "A security telemetry engine for detection and response"
 authors = ["Tenzir <engineering@tenzir.com>"]
 maintainers = ["Tenzir <engineering@tenzir.com>"]

version.json

@@ -4,14 +4,14 @@
     "annotated git tag without the leading 'v'.",
     "This value gets updated automatically by `scripts/prepare-release`."
   ],
-  "tenzir-version-fallback": "4.0.0-rc5",
+  "tenzir-version-fallback": "4.0.0-rc6",
   "tenzir-version-rev-count_COMMENT": [
     "This value stores the ancestor count of the tagged commit, calculated",
     "with `git rev-list --count HEAD`, then incremented by 1. This operates",
     "under the assumption that the release-preparing PR contains exactly one",
     "commit and is rebased before merging."
   ],
-  "tenzir-version-rev-count": 17291,
+  "tenzir-version-rev-count": 17355,
   "tenzir-partition-version_COMMENT": [
     "The partition version. This number must be bumped alongside the release",
     "version for releases that contain major format changes to the on-disk",

web/versioned_docs/version-Tenzir v4.0-rc6/operators/transformations/unflatten.md

@@ -0,0 +1,72 @@
+# unflatten
+
+Unflattens data structures whose field names imply a nested structure.
+
+## Synopsis
+
+```
+unflatten [<separator>]
+```
+
+## Description
+
+The `unflatten` operator creates nested records out of record entries whose
+names include a separator, thus unflattening
+
+:::info
+`unflatten` uses a heuristic to determine the unflattened schema. Thus, the
+schema of a record that has been flattened using the [`flatten`](flatten.md) operator and
+unflattened afterwards may not be identical to the schema of the unmodified
+record.
+:::
+
+### `<separator>`
+
+The separator string to unflatten records with.
+
+Defaults to `.`.
+
+## Examples
+
+Consider the following data:
+
+```json
+{
+  "src_ip": "147.32.84.165",
+  "src_port": 1141,
+  "dest_ip": "147.32.80.9",
+  "dest_port": 53,
+  "event_type": "dns",
+  "dns.type": "query",
+  "dns.id": 553,
+  "dns.rrname": "irc.freenode.net",
+  "dns.rrtype": "A",
+  "dns.tx_id": 0,
+  "dns.grouped.A": ["tenzir.com"]
+}
+```
+
+The `unflatten` operator recreates nested records from fields that contain the `.`
+separator:
+
+```json
+{
+  "src_ip": "147.32.84.165",
+  "src_port": 1141,
+  "dest_ip": "147.32.80.9",
+  "dest_port": 53,
+  "event_type": "dns",
+  "dns": {
+    "type": "query",
+    "id": 553,
+    "rrname": "irc.freenode.net",
+    "rrtype": "A",
+    "tx_id": 0,
+    "grouped": {
+      "A": [
+        "tenzir.com"
+      ]
+    }
+  }
+}
+```

web/versions.json

@@ -1,5 +1,5 @@
 [
-  "Tenzir v4.0-rc5",
+  "Tenzir v4.0-rc6",
   "VAST v3.1",
   "VAST v3.0"
 ]