@twin.org/node 0.9.1-next.4 → 0.9.1-next.5

package/dist/locales/en.json

@@ -647,7 +647,6 @@
 			"autoStartFailed": "Provider auto-start of a requested transfer failed (consumerPid: {consumerPid})",
 			"autoStartPublicOriginMissing": "Cannot auto-start the transfer: this node's public origin could not be resolved; holding the transfer in REQUESTED (consumerPid: {consumerPid})",
 			"transferProcessNotFound": "Transfer Process not found",
-			"pullTransfersNotSupported": "PULL transfers are not supported. Configure dataPlanePath in service configuration to enable PULL transfers.",
 			"transferProcessTerminated": "Transfer Process \"{consumerPid}\" is terminated and cannot be used",
 			"transferProcessTerminatedProvider": "Transfer Process \"{providerPid}\" is terminated and cannot be used",
 			"invalidTransferRequest": "Transfer Request does not conform to Dataspace Protocol specification",
@@ -688,9 +687,6 @@
 			"callerNotAuthorizedAsProvider": "The caller's verified identity does not match the provider for this transfer process",
 			"callerNotAuthorizedForTransfer": "The caller's verified identity does not match the consumer or provider for this transfer process",
 			"multipleAssignersNotSupported": "Multiple assigners found in agreement, which is not supported. Only single assigner agreements are supported.",
-			"invalidPushDataAddress": "PUSH transfer cannot start: consumer dataAddress is missing endpoint or endpointType (consumerPid: {consumerPid})",
-			"pushTransferDataPathNotConfigured": "PUSH transfer cannot start: dataPlanePath is not configured (consumerPid: {consumerPid})",
-			"dataPlaneNotRegistered": "Push-mode transfer requires the data plane component to be registered (factory key: \"dataspace-data-plane\"). This deployment was configured without a data plane — register one to enable push, or use pull-mode transfers only.",
 			"datasetPublishFailed": "Failed to publish dataset \"{datasetId}\" for app \"{appId}\" (tenant: \"{tenantId}\")",
 			"datasetRemoveFailed": "Failed to remove dataset \"{datasetId}\" from the Federated Catalogue (tenant: \"{tenantId}\")",
 			"datasetAlreadyExists": "A dataset with id \"{existingId}\" already exists.",
@@ -700,6 +696,18 @@
 			"invalidDatasetId": "Dataset ID \"{id}\" is not a valid URN or URL"
 		},
 		"dataspaceControlPlanePolicyRequester": {},
+		"httpDataPullTransferHandler": {
+			"pullTransfersNotSupported": "PULL transfers are not supported: dataPlanePath is not configured (consumerPid: {consumerPid}, providerPid: {providerPid})",
+			"providerIdentityMissing": "Provider identity (DID) is required to sign data access tokens but was not set on the Transfer Process"
+		},
+		"httpDataPushTransferHandler": {
+			"pushTransferDataPathNotConfigured": "PUSH transfer cannot start: dataPlanePath is not configured (consumerPid: {consumerPid})",
+			"invalidPushDataAddress": "PUSH transfer cannot start: consumer dataAddress is missing endpoint or endpointType (consumerPid: {consumerPid})"
+		},
+		"httpDataPostTransferHandler": {
+			"pushTransferDataPathNotConfigured": "POST transfer cannot start: dataPlanePath is not configured (consumerPid: {consumerPid})",
+			"providerIdentityMissing": "Provider identity (DID) is required to sign data access tokens but was not set on the Transfer Process"
+		},
 		"trustHelper": {
 			"trustVerifyFailed": "Trust verification failed for action \"{action}\""
 		},
@@ -2342,7 +2350,6 @@
 			"transferProcessInitiated": "Transfer Process initiated",
 			"transferProcessQueried": "Transfer Process queried (role: {role})",
 			"transferProcessStarted": "Transfer Process started",
-			"dataAccessTokenGenerated": "Data access token generated for PULL transfer",
 			"transferProcessCompleted": "Transfer Process completed",
 			"transferProcessSuspended": "Transfer Process suspended",
 			"transferProcessTerminated": "Transfer Process terminated",
@@ -2363,7 +2370,6 @@
 			"negotiationHistoryRetrieved": "Negotiation history retrieved successfully",
 			"stalledNegotiationsCleanupComplete": "Stalled negotiations cleanup completed (cleanedUp: {cleanedUp})",
 			"stalledTransfersCleanupComplete": "Stalled transfers cleanup completed (cleanedUp: {cleanedUp})",
-			"pushTransferStarted": "PUSH transfer started (consumerPid: {consumerPid}, providerPid: {providerPid}, endpoint: {endpoint})",
 			"preparingTransfer": "Preparing consumer-initiated data transfer (agreementId: {agreementId}, providerEndpoint: {providerEndpoint}, format: {format})",
 			"transferPrepared": "Consumer data transfer prepared successfully (consumerPid: {consumerPid}, providerPid: {providerPid}, agreementId: {agreementId}, format: {format})"
 		},

package/docs/changelog.md

@@ -1,5 +1,19 @@
 # Changelog
 
+## [0.9.1-next.5](https://github.com/iotaledger/twin-node/compare/node-v0.9.1-next.4...node-v0.9.1-next.5) (2026-07-02)
+
+
+### Features
+
+* dataspace plane path ([#272](https://github.com/iotaledger/twin-node/issues/272)) ([5998eeb](https://github.com/iotaledger/twin-node/commit/5998eeb6fa1392ae753eb6bafeccefa1fb690573))
+
+
+### Dependencies
+
+* The following workspace dependencies were updated
+  * dependencies
+    * @twin.org/node-core bumped from 0.9.1-next.4 to 0.9.1-next.5
+
 ## [0.9.1-next.4](https://github.com/iotaledger/twin-node/compare/node-v0.9.1-next.3...node-v0.9.1-next.4) (2026-07-01)
 
 

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@twin.org/node",
-	"version": "0.9.1-next.4",
+	"version": "0.9.1-next.5",
 	"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.9.1-next.4"
+		"@twin.org/node-core": "0.9.1-next.5"
 	},
 	"bugs": {
 		"url": "git+https://github.com/iotaledger/twin-node/issues"