@twin.org/node 0.0.3-next.64 → 0.0.3-next.66

package/docs/changelog.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## [0.0.3-next.66](https://github.com/iotaledger/twin-node/compare/node-v0.0.3-next.65...node-v0.0.3-next.66) (2026-06-23)
+
+
+### Features
+
+* add standalone federated catalogue example config and endpoint tests ([#235](https://github.com/iotaledger/twin-node/issues/235)) ([ffb51dd](https://github.com/iotaledger/twin-node/commit/ffb51ddda5188c2f21b8ce65343b39a28f4eee4b))
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @twin.org/node-core bumped from 0.0.3-next.65 to 0.0.3-next.66
+
+## [0.0.3-next.65](https://github.com/iotaledger/twin-node/compare/node-v0.0.3-next.64...node-v0.0.3-next.65) (2026-06-23)
+
+
+### Miscellaneous Chores
+
+* **node:** Synchronize repo versions
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @twin.org/node-core bumped from 0.0.3-next.64 to 0.0.3-next.65
+
 ## [0.0.3-next.64](https://github.com/iotaledger/twin-node/compare/node-v0.0.3-next.63...node-v0.0.3-next.64) (2026-06-23)
 
 

package/docs/configuration.md

@@ -1,5 +1,16 @@
 # Node Configuration
 
+## Available Example Configurations
+
+Four ready-to-use example files are provided in `apps/node/`. Copy the relevant file to `.env` as a starting point:
+
+| File                                | Role                                                                      |
+| ----------------------------------- | ------------------------------------------------------------------------- |
+| `.env.example-local-entity-storage` | Full-featured node using local file/entity storage                        |
+| `.env.example-aws-ec2`              | Full-featured node deployed on Amazon AWS EC2 with DynamoDB               |
+| `.env.example-iota-testnet`         | Full-featured node connected to the IOTA testnet                          |
+| `.env.example-federated-catalogue`  | Standalone federated catalogue server (no dataspace or rights management) |
+
 ## Extension Loading
 
 The TWIN Node supports loading extensions dynamically to extend its functionality. Extensions can be loaded from multiple sources using protocol-based syntax.

package/docs/deployment-ec2.md

@@ -99,7 +99,7 @@ cd apps
 npm install
 npm run dist
 cd apps/node
-cp .env.example-entity-storage .env
+cp .env.example-local-entity-storage .env
 ```
 
 The .env file can be modified to suit your own use case. For example to set the location for the storage.

package/docs/open-api/spec.json

@@ -9899,7 +9899,7 @@
 				"parameters": [
 					{
 						"name": "id",
-						"description": "The rule id to set.",
+						"description": "The id of the rule group to set.",
 						"in": "path",
 						"required": true,
 						"schema": {
@@ -10011,7 +10011,7 @@
 				"parameters": [
 					{
 						"name": "id",
-						"description": "The rule id to set.",
+						"description": "The id of the rule group to retrieve.",
 						"in": "path",
 						"required": true,
 						"schema": {
@@ -10120,7 +10120,7 @@
 				"parameters": [
 					{
 						"name": "id",
-						"description": "The rule id to remove.",
+						"description": "The id of the rule group to remove.",
 						"in": "path",
 						"required": true,
 						"schema": {
@@ -21593,7 +21593,7 @@
 				"required": [
 					"data"
 				],
-				"description": "The params for the convert."
+				"description": "The request body containing the data to convert."
 			},
 			"DataProcessingConvertResponse": {
 				"description": "The converted data as an object."
@@ -21622,10 +21622,10 @@
 					"ruleGroupId",
 					"data"
 				],
-				"description": "The params for the extract."
+				"description": "The request body containing the data and rule group to use for extraction."
 			},
 			"DataProcessingExtractResponse": {
-				"description": "The extracted data in extended JSON format which keeps types like bigint, dates and uint8array intact.\nUse ObjectHelper.fromExtended to get the object with original types."
+				"description": "The extracted data in extended JSON format, preserving types such as bigint, dates, and Uint8Array."
 			},
 			"DataProcessingRuleGroupListResponse": {
 				"type": "object",
@@ -21645,7 +21645,7 @@
 				"required": [
 					"entities"
 				],
-				"description": "The response payload."
+				"description": "The response body containing the list of rule groups and optional pagination cursor."
 			},
 			"DataProcessingRuleGroupSetRequest": {
 				"type": "object",
@@ -21666,7 +21666,7 @@
 					"label",
 					"rules"
 				],
-				"description": "The data to be used in the store."
+				"description": "The rule group data to store."
 			},
 			"DatasetGetResponse": {
 				"anyOf": [
@@ -23018,14 +23018,11 @@
 				"properties": {
 					"source": {
 						"type": "string",
-						"description": "The path to the data in the document to extract.\nshould be in JSONPath format https://www.rfc-editor.org/rfc/rfc9535.html."
+						"description": "The JSONPath expression identifying the data to extract from the document."
 					},
 					"target": {
 						"type": "string",
-						"description": "The target path of where to store the extracted data.\nSupports simple dotted path notation, and numeric index notation.",
-						"examples": [
-							"\"path.to.data\" or \"path.to.data.0\""
-						]
+						"description": "The target path of where to store the extracted data, using dotted or numeric index notation."
 					},
 					"retainPathDepth": {
 						"type": "number",

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@twin.org/node",
-	"version": "0.0.3-next.64",
+	"version": "0.0.3-next.66",
 	"description": "TWIN Node serving APIs using the specified configuration",
 	"repository": {
 		"type": "git",
@@ -14,7 +14,7 @@
 		"node": ">=20.0.0"
 	},
 	"dependencies": {
-		"@twin.org/node-core": "0.0.3-next.64"
+		"@twin.org/node-core": "0.0.3-next.66"
 	},
 	"bugs": {
 		"url": "git+https://github.com/iotaledger/twin-node/issues"