Skip to content

Coinbase main#90

Merged
Dargon789 merged 4 commits intomainfrom
coinbase-main
Mar 17, 2026
Merged

Coinbase main#90
Dargon789 merged 4 commits intomainfrom
coinbase-main

Conversation

@Dargon789
Copy link
Copy Markdown
Owner

What changed? Why?

Notes to reviewers

How has it been tested?

Dargon789 and others added 2 commits February 2, 2026 02:06
…#86)

* Add quickAuth example to MiniKit example app (coinbase#2429)

* feat: Add Base Account connector support (coinbase#2435)

* chore: version packages 🚀 (coinbase#2432)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dan Cortes <3639170+dgca@users.noreply.github.com>

* extended validation to max 8 chars (coinbase#2437)

* chore: Use github changesets generator (coinbase#2438)

* chore: Manifest validator changeset (coinbase#2440)

* chore: Tweak changeset formatter order (coinbase#2442)

* feat: Add useSwapToken util (coinbase#2444)

* feat: useSendToken hook (coinbase#2445)

* fix: Export useSendToken, add example (coinbase#2446)

* chore: version packages 🚀 (coinbase#2441)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* fix: useFundCardSetupOnrampEventListeners unmount reset (coinbase#2182)

* feat: use crypto api for nonce generation (coinbase#2303)

* fix: useDebounce cleanup (coinbase#2305)

* chore(deps): bump next from 14.2.26 to 14.2.32 (coinbase#2471)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore(deps-dev): bump vite from 5.4.19 to 5.4.20 (coinbase#2483)

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat: OnchainKit@v1 (coinbase#2415)

* chore: Remove deprecated schemaId prop (coinbase#2490)

* fix: Remove deprecated cacheTime arg (coinbase#2493)

* fix: Fix onchainkit and create-onchain versions (coinbase#2496)

* Release create-onchain v1 (coinbase#2497)

* chore: version packages 🚀 (coinbase#2498)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dan Cortes <3639170+dgca@users.noreply.github.com>

* chore: Release onchainkit and create-onchain at 1.0.2 (coinbase#2499)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* fix: Minikit template prepends process.env.VERCEL_URL with https:// (coinbase#2502)

* fix: Add `baseBuilder.allowedAddresses` to template + call `setFrameReady()` automatically (coinbase#2503)

* chore: Add changeset to create-onchain (coinbase#2504)

* chore: version packages 🚀 (coinbase#2505)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Dan Cortes <3639170+dgca@users.noreply.github.com>

* chore(ONRAMP-843): FundCard accept sessionToken param (coinbase#2501)

* feat: Allow useOpenUrl to specify fallback behavior (coinbase#2500)

* fix: Rename setFrameReady and isFrameReady (coinbase#2510)

* fix: Update GetOnrampUrl type (coinbase#2511)

* chore: version packages 🚀 (coinbase#2509)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* fix: Allow additional properties in `withValidManifest` (coinbase#2515)

* chore: version packages 🚀 (coinbase#2516)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* fix: Deprecate useNotifications hook (coinbase#2527)

* fix: Deprecate Checkout component (coinbase#2528)

* fix: Rename allowedAddresses to ownerAddress (coinbase#2530)

* chore: version packages 🚀 (coinbase#2529)

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>

* chore: fix fund components to mandate session-token (coinbase#2542)

* chore: bump react/next due to recent cve (coinbase#2554)
e1b37c5
---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: Dan Cortes <3639170+dgca@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Sohey <soheimam@gmail.com>
Co-authored-by: Teimur Gasanov <teymurgg321@gmail.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: Rustam Goygov <139204496+rustam-cb@users.noreply.github.com>
Co-authored-by: suryatejamandadi-cb <suryateja.mandadi@coinbase.com>
Co-authored-by: Dylan Steck <dylancsteck@gmail.com>
@vercel

This comment was marked as resolved.

@snyk-io
Copy link
Copy Markdown

snyk-io bot commented Feb 2, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @Dargon789, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request lays foundational infrastructure for the project by integrating a basic continuous integration pipeline using CircleCI and establishing a standard security policy document. These additions are crucial for setting up initial development workflows and communicating essential security guidelines.

Highlights

  • Initial CI Configuration: A basic CircleCI configuration file (.circleci/config.yml) has been added, setting up a simple 'say-hello' job and workflow to establish continuous integration capabilities.
  • Security Policy Document: A standard SECURITY.md file has been introduced, providing a template for outlining supported versions and procedures for reporting vulnerabilities.
Ignored Files
  • Ignored by pattern: .github/workflows/** (2)
    • .github/workflows/dependency-review.yml
    • .github/workflows/stale.yml
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request adds a basic CircleCI configuration and a template for a security policy. The CircleCI configuration is a good starting point, but I've suggested pinning the Docker image version to ensure reproducible builds and adding a final newline to adhere to standard conventions. The SECURITY.md file is currently a placeholder and needs to be filled out with specific details about supported versions and, most importantly, the process for reporting vulnerabilities.

I am having trouble creating individual review comments. Click here to see my feedback.

.circleci/config.yml (14)

medium

For reproducible builds, it's recommended to pin the Docker image to a specific version instead of using the current tag. The current tag can change unexpectedly, potentially breaking your build pipeline. You can find available versioned tags on the CircleCI Developer Hub.

      - image: cimg/base:2024.01

.circleci/config.yml (31)

medium

This file is missing a final newline. It's a common convention and POSIX standard to end text files with a newline character. Many tools work better with files that end with a newline.

SECURITY.md (5-21)

security-medium medium

This security policy file appears to be a template and contains placeholder content. Please update the following sections with project-specific information:

  • Supported Versions: The version table should reflect the actual versions of your project that receive security updates.
  • Reporting a Vulnerability: This section is critical and needs clear instructions on how to report a vulnerability, including contact details and the expected process.

@vercel
Copy link
Copy Markdown

vercel bot commented Mar 17, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
onchainkit-minikit-example Ready Ready Preview, Comment Mar 17, 2026 0:37am

@vercel

This comment was marked as resolved.

@github-actions
Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

@Dargon789
Copy link
Copy Markdown
Owner Author

@Mergifyio refresh

@Dargon789
Copy link
Copy Markdown
Owner Author

@Mergifyio update

@Dargon789 Dargon789 merged commit 8083677 into main Mar 17, 2026
14 of 22 checks passed
@mergify
Copy link
Copy Markdown

mergify bot commented Mar 17, 2026

update

❌ Base branch update has failed

Details

merge conflict between base and head

@Dargon789
Copy link
Copy Markdown
Owner Author

@Mergifyio refresh

@mergify
Copy link
Copy Markdown

mergify bot commented Mar 17, 2026

refresh

✅ Pull request refreshed

@Dargon789
Copy link
Copy Markdown
Owner Author

@Mergifyio rebase

@mergify
Copy link
Copy Markdown

mergify bot commented Mar 17, 2026

refresh

✅ Pull request refreshed

@mergify
Copy link
Copy Markdown

mergify bot commented Mar 17, 2026

rebase

☑️ Nothing to do, the required conditions are not met

Details
  • -closed [📌 rebase requirement]
  • -conflict [📌 rebase requirement]
  • queue-position = -1 [📌 rebase requirement]
  • any of:
    • -linear-history [📌 rebase requirement]
    • #commits-behind > 0 [📌 rebase requirement]

@Dargon789 Dargon789 linked an issue Mar 17, 2026 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[vc]: #[Snyk] Security upgrade express from 4.21.2 to 4.22.0#97

1 participant