Feature/x402 node #55

manu-xmint · 2025-11-01T10:47:47Z

Fix Coinbase CDP API schema validation errors in x402 payment verification

Summary

Fixed a 400 Bad Request error from Coinbase CDP API that was occurring during x402 payment verification. The error was: "request body has an error: doesn't match schema: value doesn't match any schema from oneOf".

The root causes were:

Duplicate x402Version field (both top-level and nested in paymentPayload)
Extra fields in paymentRequirements that Coinbase doesn't accept
Network value mismatch (solana-devnet vs solana)
Type inconsistency in x402Version between interface and validation

Changes made:

Removed duplicate top-level x402Version from request body sent to Coinbase
Trimmed paymentRequirements to only include fields Coinbase expects: scheme, network, payTo, maxAmountRequired, asset
Added network normalization to convert solana-devnet → solana for Coinbase API compatibility
Fixed x402Version type from string to number in IPaymentPayload interface to match validation logic

Review & Testing Checklist for Human

⚠️ CRITICAL - This fix has NOT been tested end-to-end with real Coinbase API calls

Test with real Coinbase credentials: Use the test script provided by the user with the Coinbase ECDSA credentials. The webhook should accept x402 payments without the schema validation error.
Verify network normalization: Confirm that converting solana-devnet → solana is correct for Coinbase API. Check if this breaks devnet testing or if Coinbase expects the original network value.
Validate against Coinbase API schema: Review Coinbase CDP API documentation to confirm that the trimmed paymentRequirements fields match their /platform/v2/x402/verify and /platform/v2/x402/settle schemas.
Check for x402Version type change impacts: Verify no other code paths were broken by changing x402Version from string to number in the IPaymentPayload interface.

Test Plan

Set up n8n with the webhook node using staging environment
Configure a payment token (USDC or SOL on Solana devnet)
Use the provided test script with Coinbase credentials to make a payment request
Verify the webhook receives and processes the payment without 400 errors
Check that both verify and settle API calls succeed

Notes

Build and TypeScript compilation passed successfully
Lint errors shown are pre-existing in the codebase, not introduced by these changes
The fix was based on analyzing the error message and smart friend consultation, but without access to official Coinbase x402 schema documentation
Session: https://app.devin.ai/sessions/0795e7ac1acf4b25819691842b21209a
Requested by: [email protected] (@manu-xmint)

greptile-apps

I'm learning! Leave a 👍 or a 👎 to help me learn. Extra points if you leave a comment telling me why i'm wrong tagging @greptileai

_{13 files reviewed, 3 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2025-11-01T10:49:43Z

nodes/webhooks/executions/validation/paymentValidation.ts

+			if (typeof actual[key] !== 'object' || actual[key] === null) {
+				missing.push('Invalid type at ' + currentPath + ': expected object');
+			} else {
+				checkShape(expected[key], actual[key], currentPath);


logic: checkShape recursive call doesn't accumulate errors from nested validation

Suggested change

checkShape(expected[key], actual[key], currentPath);

missing.push(...checkShape(expected[key], actual[key], currentPath));

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/validation/paymentValidation.ts Line: 50:50 Comment: **logic:** `checkShape` recursive call doesn't accumulate errors from nested validation ```suggestion missing.push(...checkShape(expected[key], actual[key], currentPath)); ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-01T10:49:44Z

nodes/webhooks/executions/Webhooks.ts

+import { generateX402Error, generateResponse } from './response/paymentResponse';
+
+export async function webhookTrigger(this: IWebhookFunctions): Promise<IWebhookResponseData> {
+	console.log("AAAAAAAA");


style: Remove debug log statement

Suggested change

console.log("AAAAAAAA");

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/Webhooks.ts Line: 13:13 Comment: **style:** Remove debug log statement ```suggestion ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-01T10:49:44Z

nodes/webhooks/CrossmintWebhooks.node.ts

+								type: 'string',
+								required: true,


logic: Misleading description - says "EVM address with leading 0x" but this node is for Solana tokens (SOL/USDC), which use base58-encoded addresses, not EVM addresses

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/CrossmintWebhooks.node.ts Line: 165:166 Comment: **logic:** Misleading description - says "EVM address with leading 0x" but this node is for Solana tokens (SOL/USDC), which use base58-encoded addresses, not EVM addresses How can I resolve this? If you propose a fix, please make it concise.

greptile-apps

I'm learning! Leave a 👍 or a 👎 to help me learn. Extra points if you leave a comment telling me why i'm wrong tagging @greptileai

_{2 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2025-11-01T11:12:21Z

nodes/webhooks/executions/types/x402Types.ts

@@ -0,0 +1,53 @@
+export interface IPaymentPayload {
+	x402Version: number;


logic: Type mismatch - x402Version changed from string to number but validation expects 'number' type, and the facilitator converts it with String(). Check if incoming x-payment headers actually send numbers or strings.

If headers send strings, this breaks validation at paymentValidation.ts:50. If they send numbers, the String() conversion works but seems unnecessary.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/types/x402Types.ts Line: 2:2 Comment: **logic:** Type mismatch - `x402Version` changed from `string` to `number` but validation expects `'number'` type, and the facilitator converts it with `String()`. Check if incoming x-payment headers actually send numbers or strings. If headers send strings, this breaks validation at `paymentValidation.ts:50`. If they send numbers, the `String()` conversion works but seems unnecessary. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps

I'm learning! Leave a 👍 or a 👎 to help me learn. Extra points if you leave a comment telling me why i'm wrong tagging @greptileai

_{7 files reviewed, 5 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2025-11-03T00:22:50Z

nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts

+	const paymentRequirementsObj: IPaymentRequirements = {
+		scheme: paymentRequirements.scheme,
+		network: paymentRequirements.network,
+		maxAmountRequired: paymentRequirements.maxAmountRequired,
+		resource: paymentRequirements.resource,
+		description: paymentRequirements.description,
+		mimeType: paymentRequirements.mimeType,
+		outputSchema: paymentRequirements.outputSchema,
+		payTo: paymentRequirements.payTo,
+		maxTimeoutSeconds: paymentRequirements.maxTimeoutSeconds,
+		asset: paymentRequirements.asset,
+		extra: paymentRequirements.extra,
+	};


logic: PR description claims "Trimmed paymentRequirements to only include fields Coinbase expects: scheme, network, payTo, maxAmountRequired, asset" but this code still includes ALL fields (resource, description, mimeType, outputSchema, maxTimeoutSeconds, extra). If Coinbase rejects extra fields, this hasn't been fixed.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts Line: 40:52 Comment: **logic:** PR description claims "Trimmed `paymentRequirements` to only include fields Coinbase expects: `scheme`, `network`, `payTo`, `maxAmountRequired`, `asset`" but this code still includes ALL fields (`resource`, `description`, `mimeType`, `outputSchema`, `maxTimeoutSeconds`, `extra`). If Coinbase rejects extra fields, this hasn't been fixed. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T00:22:51Z

nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts

+		extra: paymentRequirements.extra,
+	};
+	const requestBody = {
+		x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,


logic: Duplicate x402Version at both top level AND nested in paymentPayload. PR description says this was fixed ("Removed duplicate top-level x402Version"), but both are still present in the request body.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts Line: 54:54 Comment: **logic:** Duplicate `x402Version` at both top level AND nested in `paymentPayload`. PR description says this was fixed ("Removed duplicate top-level `x402Version`"), but both are still present in the request body. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T00:22:52Z

nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts

+		x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,
+		paymentPayload: {
+			...paymentPayload,
+			x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,
+		},


logic: Type conversion logic assumes x402Version might not be a string, but IPaymentPayload interface at types/x402Types.ts:3 defines it as string, and validation at validation/paymentValidation.ts:11 expects 'string'. If incoming data is always a string per the interface, this defensive check is unnecessary. If it can be a number, the interface/validation are wrong.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts Line: 54:58 Comment: **logic:** Type conversion logic assumes `x402Version` might not be a string, but `IPaymentPayload` interface at `types/x402Types.ts:3` defines it as `string`, and validation at `validation/paymentValidation.ts:11` expects `'string'`. If incoming data is always a string per the interface, this defensive check is unnecessary. If it can be a number, the interface/validation are wrong. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T00:22:52Z

nodes/webhooks/executions/helpers/paymentHelpers.ts

+		}
+
+		// Map 'base' to the expected network (base or base-sepolia based on environment)
+		const normalizedNetwork = network === 'base' ? expectedNetwork : network;


logic: Network normalization only handles 'base' → expectedNetwork mapping. PR description mentions "converting solana-devnet → solana" but no such normalization exists in the code. If Coinbase expects solana instead of solana-devnet, payments will fail.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/helpers/paymentHelpers.ts Line: 60:60 Comment: **logic:** Network normalization only handles `'base'` → `expectedNetwork` mapping. PR description mentions "converting `solana-devnet` → `solana`" but no such normalization exists in the code. If Coinbase expects `solana` instead of `solana-devnet`, payments will fail. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T00:22:53Z

nodes/webhooks/executions/helpers/paymentHelpers.ts

+		// Convert payment amount to atomic units (USDC has 6 decimals)
+		// If paymentAmount is already in atomic units (integer >= 1000000), use it as-is
+		// Otherwise, assume it's in dollars and multiply by 10^6
+		const paymentAmountInAtomicUnits = configuredToken.paymentAmount < 1000000
+			? Math.floor(configuredToken.paymentAmount * 1000000)
+			: configuredToken.paymentAmount;


logic: Heuristic breaks for payments < $1 in atomic units. E.g., 500000 atomic units ($0.50) gets incorrectly multiplied by 10^6 → 500000000000 ($500k). The node description at CrossmintWebhooks.node.ts:178 says "in atomic units (must be an integer)", so this conversion shouldn't exist. Either remove the heuristic or update the UI description to clarify it accepts both formats.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/helpers/paymentHelpers.ts Line: 78:83 Comment: **logic:** Heuristic breaks for payments < $1 in atomic units. E.g., 500000 atomic units ($0.50) gets incorrectly multiplied by 10^6 → 500000000000 ($500k). The node description at `CrossmintWebhooks.node.ts:178` says "in atomic units (must be an integer)", so this conversion shouldn't exist. Either remove the heuristic or update the UI description to clarify it accepts both formats. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps

I'm learning! Leave a 👍 or a 👎 to help me learn. Extra points if you leave a comment telling me why i'm wrong tagging @greptileai

_{8 files reviewed, 5 comments}

_{Edit Code Review Agent Settings | Greptile}

greptile-apps · 2025-11-03T22:27:27Z

nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts

+		x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,
+		paymentPayload: {
+			...paymentPayload,
+			x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,
+		},


logic: PR claims "Removed duplicate top-level x402Version" but both still exist. Line 54 sets top-level x402Version AND line 57 sets it again inside nested paymentPayload. This creates the exact duplicate field issue the PR was supposed to fix.

Suggested change

x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,

paymentPayload: {

...paymentPayload,

x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,

},

const requestBody = {

paymentPayload: {

...paymentPayload,

x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1,

},

paymentRequirements: paymentRequirementsObj,

};

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts Line: 54:58 Comment: **logic:** PR claims "Removed duplicate top-level `x402Version`" but both still exist. Line 54 sets top-level `x402Version` AND line 57 sets it again inside nested `paymentPayload`. This creates the exact duplicate field issue the PR was supposed to fix. ```suggestion const requestBody = { paymentPayload: { ...paymentPayload, x402Version: typeof paymentPayload.x402Version === 'string' ? parseInt(paymentPayload.x402Version, 10) : paymentPayload.x402Version ?? 1, }, paymentRequirements: paymentRequirementsObj, }; ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T22:27:28Z

nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts

+	const paymentRequirementsObj: IPaymentRequirements = {
+		scheme: paymentRequirements.scheme,
+		network: paymentRequirements.network,
+		maxAmountRequired: paymentRequirements.maxAmountRequired,
+		resource: paymentRequirements.resource,
+		description: paymentRequirements.description,
+		mimeType: paymentRequirements.mimeType,
+		outputSchema: paymentRequirements.outputSchema,
+		payTo: paymentRequirements.payTo,
+		maxTimeoutSeconds: paymentRequirements.maxTimeoutSeconds,
+		asset: paymentRequirements.asset,
+		extra: paymentRequirements.extra,
+	};


logic: PR claims "Trimmed paymentRequirements to only include fields Coinbase expects: scheme, network, payTo, maxAmountRequired, asset" but ALL original fields remain (resource, description, mimeType, outputSchema, maxTimeoutSeconds, extra). The supposed trimming never happened - these extra fields will still cause Coinbase API rejection.

Suggested change

const paymentRequirementsObj: IPaymentRequirements = {

scheme: paymentRequirements.scheme,

network: paymentRequirements.network,

maxAmountRequired: paymentRequirements.maxAmountRequired,

resource: paymentRequirements.resource,

description: paymentRequirements.description,

mimeType: paymentRequirements.mimeType,

outputSchema: paymentRequirements.outputSchema,

payTo: paymentRequirements.payTo,

maxTimeoutSeconds: paymentRequirements.maxTimeoutSeconds,

asset: paymentRequirements.asset,

extra: paymentRequirements.extra,

};

const paymentRequirementsObj: IPaymentRequirements = {

scheme: paymentRequirements.scheme,

network: paymentRequirements.network,

payTo: paymentRequirements.payTo,

maxAmountRequired: paymentRequirements.maxAmountRequired,

asset: paymentRequirements.asset,

};

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/facilitator/coinbaseFacilitator.ts Line: 40:52 Comment: **logic:** PR claims "Trimmed `paymentRequirements` to only include fields Coinbase expects: `scheme`, `network`, `payTo`, `maxAmountRequired`, `asset`" but ALL original fields remain (`resource`, `description`, `mimeType`, `outputSchema`, `maxTimeoutSeconds`, `extra`). The supposed trimming never happened - these extra fields will still cause Coinbase API rejection. ```suggestion const paymentRequirementsObj: IPaymentRequirements = { scheme: paymentRequirements.scheme, network: paymentRequirements.network, payTo: paymentRequirements.payTo, maxAmountRequired: paymentRequirements.maxAmountRequired, asset: paymentRequirements.asset, }; ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T22:27:29Z

nodes/webhooks/executions/types/x402Types.ts

@@ -0,0 +1,54 @@
+// EVM exact scheme payload structure (EIP-3009)
+export interface IPaymentPayload {
+	x402Version: string;


logic: Type mismatch breaks validation. Interface defines x402Version: string but paymentValidation.ts:11 expects 'number' type, causing validation to fail with "Invalid type at x402Version: expected number, got string". Either change this to number or fix validation to expect 'string'.

Suggested change

x402Version: string;

x402Version: number;

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/types/x402Types.ts Line: 3:3 Comment: **logic:** Type mismatch breaks validation. Interface defines `x402Version: string` but `paymentValidation.ts:11` expects `'number'` type, causing validation to fail with "Invalid type at x402Version: expected number, got string". Either change this to `number` or fix validation to expect `'string'`. ```suggestion x402Version: number; ``` How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T22:27:30Z

nodes/webhooks/executions/helpers/paymentHelpers.ts

+			return null;
+		}
+
+		// Map 'base' to the expected network (base or base-sepolia based on environment)


logic: PR claims "Added network normalization to convert solana-devnet → solana" but only 'base' → expectedNetwork mapping exists. No solana-devnet normalization implemented - Coinbase API calls will fail if it expects solana instead of solana-devnet.

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/helpers/paymentHelpers.ts Line: 59:59 Comment: **logic:** PR claims "Added network normalization to convert `solana-devnet` → `solana`" but only `'base'` → `expectedNetwork` mapping exists. No solana-devnet normalization implemented - Coinbase API calls will fail if it expects `solana` instead of `solana-devnet`. How can I resolve this? If you propose a fix, please make it concise.

greptile-apps · 2025-11-03T22:27:31Z

nodes/webhooks/executions/helpers/paymentHelpers.ts

+		// Convert payment amount to atomic units (USDC has 6 decimals)
+		// If paymentAmount is already in atomic units (integer >= 1000000), use it as-is
+		// Otherwise, assume it's in dollars and multiply by 10^6
+		const paymentAmountInAtomicUnits = configuredToken.paymentAmount < 1000000
+			? Math.floor(configuredToken.paymentAmount * 1000000)


logic: Heuristic incorrectly converts sub-dollar amounts. E.g., 500000 atomic units (0.50 USDC) incorrectly becomes 500000000000 ($500k USDC) because 500000 < 1000000 triggers multiplication. Either remove heuristic entirely (since CrossmintWebhooks.node.ts:178 says "in atomic units") or use threshold like < 100 to detect dollar amounts.

Suggested change

// Convert payment amount to atomic units (USDC has 6 decimals)

// If paymentAmount is already in atomic units (integer >= 1000000), use it as-is

// Otherwise, assume it's in dollars and multiply by 10^6

const paymentAmountInAtomicUnits = configuredToken.paymentAmount < 1000000

? Math.floor(configuredToken.paymentAmount * 1000000)

// Only convert if value is clearly in dollars (< 100) vs atomic units (>= 100)

const paymentAmountInAtomicUnits = configuredToken.paymentAmount < 100

? Math.floor(configuredToken.paymentAmount * 1000000)

: configuredToken.paymentAmount;

Prompt To Fix With AI

This is a comment left during a code review. Path: nodes/webhooks/executions/helpers/paymentHelpers.ts Line: 78:82 Comment: **logic:** Heuristic incorrectly converts sub-dollar amounts. E.g., 500000 atomic units (0.50 USDC) incorrectly becomes 500000000000 ($500k USDC) because 500000 < 1000000 triggers multiplication. Either remove heuristic entirely (since `CrossmintWebhooks.node.ts:178` says "in atomic units") or use threshold like `< 100` to detect dollar amounts. ```suggestion // Only convert if value is clearly in dollars (< 100) vs atomic units (>= 100) const paymentAmountInAtomicUnits = configuredToken.paymentAmount < 100 ? Math.floor(configuredToken.paymentAmount * 1000000) : configuredToken.paymentAmount; ``` How can I resolve this? If you propose a fix, please make it concise.

manu and others added 6 commits October 26, 2025 02:24

CrossmintX402

4494325

Restart

4e1957a

New Webhook x402 node

ef37403

Verify Payments and Settle Payments

9c479e5

Lamports not working

cd11014

Error in schema

72f5a20

greptile-apps bot reviewed Nov 1, 2025

View reviewed changes

Only missing Signature

6f2b60c

manu-xmint force-pushed the feature/x402-node branch from 2176bd8 to 72f5a20 Compare November 3, 2025 00:18

greptile-apps bot reviewed Nov 3, 2025

View reviewed changes

Working

7cf8f1d

greptile-apps bot reviewed Nov 3, 2025

View reviewed changes

	checkShape(expected[key], actual[key], currentPath);
	missing.push(...checkShape(expected[key], actual[key], currentPath));

		@@ -0,0 +1,53 @@
		export interface IPaymentPayload {
		x402Version: number;

Feature/x402 node #55

Are you sure you want to change the base?

Feature/x402 node #55

Uh oh!

Conversation

manu-xmint commented Nov 1, 2025 • edited by devin-ai-integration bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Fix Coinbase CDP API schema validation errors in x402 payment verification

Summary

Review & Testing Checklist for Human

Test Plan

Notes

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 1, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 1, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 1, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 1, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot left a comment

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

greptile-apps bot Nov 3, 2025

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

manu-xmint commented Nov 1, 2025 •

edited by devin-ai-integration bot

Loading