Skip to content

Conversation

@shoom3301
Copy link
Contributor

No description provided.

…AIN_TO_NATIVE_WRAPPED_TOKEN_ADDRESS to support wrapped assets, changes an import and rm the sending of native tokens within getUnsignedBridgeCall
…ithin getSignedHook and implements getBridgingParams
…ment and a remove a useless check within getBridgingParams
…ithin getSignedHook, fixes getTokenByAddressAndChainId and getIntermediateTokens
…ridgeCallWithoutHooks within NearIntentsBridgeProvider
…m getUnsignedBridgeCall in favour of the balance of the sell token within the cowshed account at the swap time
…irect transfer to near deposit address within NearIntentsBridgeProvider
…col/one-click-sdk-typescript within dependencies
…TS_BLOCKCHAIN_TO_NATIVE_WRAPPED_TOKEN_ADDRESS into WRAPPED_NATIVE_CURRENCIES
allemanfredi and others added 23 commits November 8, 2025 14:45
…ermediateTokens to use targetSymbol=sourceSymbol
…vider.ts): forces token addresses to be lower case within getIntermediateTokens
…geProvider.ts): replaces Error with BridgeProviderQuoteError within getQuote
…/cow-sdk into substance-labs-feat/near-intents

# Conflicts:
#	packages/bridging/package.json
#	packages/bridging/src/providers/near-intents/NearIntentsApi.ts
#	packages/bridging/src/providers/near-intents/NearIntentsBridgeProvider.ts
#	packages/bridging/src/providers/near-intents/const/index.ts
#	packages/bridging/src/providers/near-intents/util.test.ts
#	packages/bridging/src/providers/near-intents/util.ts
#	pnpm-lock.yaml
…geProvider.ts): allows all source tokens when target token is supported within getIntermediateTokens
…abs/cow-sdk into substance-labs-feat/near-intents

# Conflicts:
#	packages/bridging/src/providers/near-intents/NearIntentsBridgeProvider.test.ts
#	packages/bridging/src/providers/near-intents/NearIntentsBridgeProvider.ts
@shoom3301 shoom3301 self-assigned this Nov 12, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 12, 2025

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch substance-labs-feat/near-intents-8

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Added@​defuse-protocol/​one-click-sdk-typescript@​0.1.1-0.2771009994100
Addedjson-schema-ref-parser@​9.0.91001009582100
Addedreact@​18.3.11001008597100
Addedreact-dom@​18.3.11001009297100

View full report

@socket-security
Copy link

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm safer-buffer is 94.0% likely obfuscated

Confidence: 0.94

Location: Package overview

From: pnpm-lock.yamlnpm/@graphql-codegen/[email protected]npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@github-actions
Copy link
Contributor

📦 GitHub Packages Published

Last updated: Nov 12, 2025, 03:48:36 PM UTC

The following packages have been published to GitHub Packages with pre-release version pr-668-7bf1ee21:


Installation

These packages require authentication to install from GitHub Packages. First, create a .npmrc file:

# Create .npmrc file in your project root
echo "@cowprotocol:registry=https://npm.pkg.github.com" > .npmrc
echo "//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN" >> .npmrc

To get your GitHub token:

  1. Go to https://github.com/settings/tokens
  2. Click "Generate new token (classic)"
  3. Check only the "read:packages" scope
  4. Copy the token and replace YOUR_GITHUB_TOKEN in the .npmrc file

Then install any of the packages above, either by exact version (i.e. @cowprotocol/[email protected]) or more conveniently by using the tag (@cowprotocol/cow-sdk@pr-668):

# Yarn
yarn add npm:@cowprotocol/cow-sdk@pr-668

# pnpm
pnpm install npm:@cowprotocol/cow-sdk@pr-668

# NPM
npm install npm:@cowprotocol/cow-sdk@pr-668

Update to the latest version (only if you used the tag)

Every commit will publish a new package. To upgrade to the latest version, run:

# Yarn
yarn upgrade @cowprotocol/cow-sdk

# pnpm
pnpm update @cowprotocol/cow-sdk

# NPM
npm update @cowprotocol/cow-sdk

View Packages

You can view the published packages at: https://github.com/cowprotocol/cow-sdk/packages

@shoom3301 shoom3301 closed this Nov 12, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Nov 12, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants