ci(release): publish latest release

Author: hello-happy-puppy

.cursor/environment.json

@@ -3,6 +3,7 @@ ignores: [
     '@graphql-codegen/*',
     '@commitlint/*',
     '@uniswap/eslint-config',
+    '@uniswap/biome-config',
     'i18next',
     'moti',
     'wrangler',
@@ -14,6 +15,11 @@ ignores: [
     'semver',
     'typanion',
     '@biomejs/biome',
+    "@nx/js",
+    "@nx/workspace",
+    "@swc/helpers",
     # needed for ci
     'dd-trace',
+    # depcheck flags itself as unused
+    'depcheck',
   ]

.depcheckrc

@@ -35,3 +35,4 @@ STATSIG_PROXY_URL_OVERRIDE=
 TRADING_API_URL_OVERRIDE=
 UNITAGS_API_URL_OVERRIDE=
 GH_TOKEN_RN_CLI=
+JUPITER_PROXY_URL=

.env.defaults

@@ -8,6 +8,20 @@ jobs:
   deploy-to-prod:
     runs-on: ubuntu-latest
     steps:
+      - uses: bullfrogsec/bullfrog@dcde5841b19b7ef693224207a7fdec67fce604db # v0.8.3
+        with:
+          # List of IPs to allow outbound connections to.
+          # By default, only localhost and IPs required for the essential operations of Github Actions are allowed.
+          # allowed-ips:|
+      
+          # List of domains to allow outbound connections to.
+          # Wildcards are accepted. For example, if allowing `*.google.com`, this will allow `www.google.com`, `console.cloud.google.com` but not `google.com`.
+          # By default, only domains required for essential operations of Github Actions and uploading job summaries are allowed.
+          # Refer to https://docs.github.com/en/actions/using-github-hosted-runners/about-github-hosted-runners/about-github-hosted-runners#communication-requirements-for-github-hosted-runners-and-github for additional domains that should be allowed for additional Github Actions features.
+          #allowed-domains: |
+          # The egress policy to enforce. Valid values are `audit` and `block`.
+          # Default: audit
+          egress-policy: audit
       - uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
 
       - name: 🧷️ Get version

.github/workflows/tag_and_release.yml

@@ -10,6 +10,7 @@ coverage
 
 # utility script output
 scripts/dist
+tools/uniswap-nx/dist
 
 # next.js
 .next/
@@ -80,4 +81,4 @@ CLAUDE.local.md
 .nx/cache
 .nx/workspace-data
 .cursor/rules/nx-rules.mdc
-.github/instructions/nx.instructions.md
+.github/instructions/nx.instructions.md

.gitignore

@@ -0,0 +1,69 @@
+#!/bin/sh
+
+if [ "$LEFTHOOK_VERBOSE" = "1" -o "$LEFTHOOK_VERBOSE" = "true" ]; then
+  set -x
+fi
+
+if [ "$LEFTHOOK" = "0" ]; then
+  exit 0
+fi
+
+call_lefthook()
+{
+  if test -n "$LEFTHOOK_BIN"
+  then
+    "$LEFTHOOK_BIN" "$@"
+  elif lefthook -h >/dev/null 2>&1
+  then
+    lefthook "$@"
+  else
+    dir="$(git rev-parse --show-toplevel)"
+    osArch=$(uname | tr '[:upper:]' '[:lower:]')
+    cpuArch=$(uname -m | sed 's/aarch64/arm64/;s/x86_64/x64/')
+    if test -f "$dir/node_modules/lefthook-${osArch}-${cpuArch}/bin/lefthook"
+    then
+      "$dir/node_modules/lefthook-${osArch}-${cpuArch}/bin/lefthook" "$@"
+    elif test -f "$dir/node_modules/@evilmartians/lefthook/bin/lefthook-${osArch}-${cpuArch}/lefthook"
+    then
+      "$dir/node_modules/@evilmartians/lefthook/bin/lefthook-${osArch}-${cpuArch}/lefthook" "$@"
+    elif test -f "$dir/node_modules/@evilmartians/lefthook-installer/bin/lefthook"
+    then
+      "$dir/node_modules/@evilmartians/lefthook-installer/bin/lefthook" "$@"
+    elif test -f "$dir/node_modules/lefthook/bin/index.js"
+    then
+      "$dir/node_modules/lefthook/bin/index.js" "$@"
+    
+    elif go tool lefthook -h >/dev/null 2>&1
+    then
+      go tool lefthook "$@"
+    elif bundle exec lefthook -h >/dev/null 2>&1
+    then
+      bundle exec lefthook "$@"
+    elif yarn lefthook -h >/dev/null 2>&1
+    then
+      yarn lefthook "$@"
+    elif pnpm lefthook -h >/dev/null 2>&1
+    then
+      pnpm lefthook "$@"
+    elif swift package lefthook >/dev/null 2>&1
+    then
+      swift package --build-path .build/lefthook --disable-sandbox lefthook "$@"
+    elif command -v mint >/dev/null 2>&1
+    then
+      mint run csjones/lefthook-plugin "$@"
+    elif uv run lefthook -h >/dev/null 2>&1
+    then
+      uv run lefthook "$@"
+    elif mise exec -- lefthook -h >/dev/null 2>&1
+    then
+      mise exec -- lefthook "$@"
+    elif devbox run lefthook -h >/dev/null 2>&1
+    then
+      devbox run lefthook "$@"
+    else
+      echo "Can't find lefthook in PATH"
+    fi
+  fi
+}
+
+call_lefthook run "post-checkout" "$@"

.husky/post-checkout

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "nx-mcp": {
+      "type": "stdio",
+      "command": "npx",
+      "args": [
+        "nx",
+        "mcp"
+      ]
+    }
+  }
+}

.mcp.json

@@ -11,6 +11,9 @@ apps/extension/build
 packages/*/dist
 packages/*/types
 
+# Ignore Generator Templates
+tools/**/generators/**/files
+
 # Ignore test coverage
 coverage
 .nyc_output
@@ -34,4 +37,4 @@ node_modules
 
 # Ignore documentation
 docs
-*.md
+*.md

.nxignore

@@ -54,8 +54,8 @@ bun mobile e2e                  # Mobile E2E tests
 ```bash
 bun g:lint:fix                  # Fix linting issues
 bun g:typecheck                 # Type check all packages
-bun g:format:fix                # Fix formatting
-bun g:fix                       # Run both lint and format fix
+bun g:format                    # Fix formatting
+bun i18n:extract                # Extract localized strings (run after changing translations)
 ```
 
 ## Architecture Overview
@@ -114,6 +114,7 @@ bun g:fix                       # Run both lint and format fix
 - Always update existing unit tests related to changes made
 - Run tests before considering a task to be 'complete'
 - Also run linting and typecheck before considering a task to be 'complete'
+- Run `bun i18n:extract` after making changes to localized strings (e.g., using translation hooks like `useTranslation`)
 
 ## Critical Development Notes
 
@@ -142,3 +143,19 @@ Core shared packages:
 ## Other Considerations
 
 Be cognizant of the app or package within which a given change is being made. Be sure to reference that app or package's respective `AGENTS.md` file and other local configuration files, including (but not limited to): `package.json`, `tsconfig.json`, etc.
+
+
+<!-- nx configuration start-->
+<!-- Leave the start & end comments to automatically receive updates. -->
+
+# General Guidelines for working with Nx
+
+- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
+- You have access to the Nx MCP server and its tools, use them to help the user
+- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
+- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
+- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
+- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+
+
+<!-- nx configuration end-->

AGENTS.md

@@ -52,10 +52,10 @@ bun mobile e2e                  # Mobile E2E tests
 ### Code Quality
 
 ```bash
-bun g:lint:fix                  # Fix linting issues
+bun g:lint:fix                  # Fix linting issues for both eslint and biome, slow
 bun g:typecheck                 # Type check all packages
-bun g:format:fix                # Fix formatting
-bun g:fix                       # Run both lint and format fix
+bun g:format                    # Fix formatting using Biome, quick
+bun i18n:extract                # Extract localized strings (run after changing translations)
 ```
 
 ## Architecture Overview
@@ -114,6 +114,7 @@ bun g:fix                       # Run both lint and format fix
 - Always update existing unit tests related to changes made
 - Run tests before considering a task to be 'complete'
 - Also run linting and typecheck before considering a task to be 'complete'
+- Run `bun i18n:extract` after making changes to localized strings (e.g., using translation hooks like `useTranslation`)
 
 ## Critical Development Notes
 
@@ -142,3 +143,19 @@ Core shared packages:
 ## Other Considerations
 
 Be cognizant of the app or package within which a given change is being made. Be sure to reference that app or package's respective `CLAUDE.md` file and other local configuration files, including (but not limited to): `package.json`, `tsconfig.json`, etc.
+
+
+<!-- nx configuration start-->
+<!-- Leave the start & end comments to automatically receive updates. -->
+
+# General Guidelines for working with Nx
+
+- When running tasks (for example build, lint, test, e2e, etc.), always prefer running the task through `nx` (i.e. `nx run`, `nx run-many`, `nx affected`) instead of using the underlying tooling directly
+- You have access to the Nx MCP server and its tools, use them to help the user
+- When answering questions about the repository, use the `nx_workspace` tool first to gain an understanding of the workspace architecture where applicable.
+- When working in individual projects, use the `nx_project_details` mcp tool to analyze and understand the specific project structure and dependencies
+- For questions around nx configuration, best practices or if you're unsure, use the `nx_docs` tool to get relevant, up-to-date docs. Always use this instead of assuming things about nx configuration
+- If the user needs help with an Nx configuration or project graph error, use the `nx_workspace` tool to get any errors
+
+
+<!-- nx configuration end-->