Merge branch 'main' into opensea-price-discovery

bosonprotocol · Apr 12, 2024 · ab9967d · ab9967d
2 parents 47c279a + 5bbcaaa
commit ab9967d
Show file tree

Hide file tree

Showing 106 changed files with 589 additions and 552 deletions.
diff --git a/.github/workflows/deploy-staging-subgraph.yaml b/.github/workflows/deploy-staging-subgraph.yaml
@@ -30,7 +30,7 @@ jobs:
         run: npm run build -- --cache-dir=".turbo"
       - name: Authenticate The Graph CLI
         run: npx graph auth --product hosted-service ${{ secrets.THE_GRAPH_ACCESS_TOKEN_STAGING }}
-      - name: Deploy subgraph to mumbai
-        run: cd ./packages/subgraph && npm run deploy:staging
+      - name: Deploy subgraph to amoy
+        run: cd ./packages/subgraph && npm run deploy:staging:amoy
       - name: Deploy subgraph to sepolia
         run: cd ./packages/subgraph && npm run deploy:staging:sepolia
diff --git a/.github/workflows/deploy-testing-subgraph.yaml b/.github/workflows/deploy-testing-subgraph.yaml
@@ -31,7 +31,7 @@ jobs:
         run: npm run build -- --cache-dir=".turbo"
       - name: Authenticate The Graph CLI
         run: npx graph auth --product hosted-service ${{ secrets.THE_GRAPH_ACCESS_TOKEN_TESTING }}
-      - name: Deploy subgraph to mumbai
-        run: cd ./packages/subgraph && npm run deploy:testing
+      - name: Deploy subgraph to amoy
+        run: cd ./packages/subgraph && npm run deploy:testing:amoy
       - name: Deploy subgraph to sepolia
         run: cd ./packages/subgraph && npm run deploy:testing:sepolia
diff --git a/.github/workflows/pin-to-pinata.yaml b/.github/workflows/pin-to-pinata.yaml
@@ -36,10 +36,10 @@ jobs:
           INFURA_PROJECT_ID: ${{ secrets.INFURA_PROJECT_ID }}
           INFURA_PROJECT_SECRET: ${{ secrets.INFURA_PROJECT_SECRET }}
         run: |
-          echo "Pin for testing/mumbai env..."
+          echo "Pin for testing/amoy env..."
           npm run pin-to-pinata -- \
             -e testing \
-            -c testing-80001-0 \
+            -c testing-80002-0 \
             -fd ${{ env.FROM_DATE }} \
             -p ${{ env.PINATA_JWT }} \
             -i ${{ env.INFURA_PROJECT_ID }}/${{ env.INFURA_PROJECT_SECRET }}
@@ -52,10 +52,10 @@ jobs:
             -p ${{ env.PINATA_JWT }} \
             -i ${{ env.INFURA_PROJECT_ID }}/${{ env.INFURA_PROJECT_SECRET }}
 
-          echo "Pin for staging/mumbai env..."
+          echo "Pin for staging/amoy env..."
           npm run pin-to-pinata -- \
             -e staging \
-            -c staging-80001-0 \
+            -c staging-80002-0 \
             -fd ${{ env.FROM_DATE }} \
             -p ${{ env.PINATA_JWT }} \
             -i ${{ env.INFURA_PROJECT_ID }}/${{ env.INFURA_PROJECT_SECRET }}

diff --git a/docs/releases.md b/docs/releases.md
@@ -24,16 +24,19 @@ Subgraphs are deployed also to different environments.
 
 Every merge into the `main` branch will trigger a deployment of the subgraph which listens to our `testing` environment. For details have a look at [`.github/workflows/deploy-testing-subgraph.yaml`](../.github/workflows/deploy-testing-subgraph.yaml.). Access this subgraph via:
 
-- https://graph.bsn-development-potassium.bosonportal.io/subgraphs/name/boson/corecomponents
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/amoy-testing
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/sepolia-testing
 
 ### Staging
 
 If a stable release of the packages are triggered through the GitHub UI, then a deployment of the subgraph connected to the `staging` environment is also initiated. For details have a look at [`.github/workflows/deploy-staging-subgraph.yaml`](../.github/workflows/deploy-staging-subgraph.yaml.). Access this subgraph via:
 
-- https://api.thegraph.com/subgraphs/name/bosonprotocol/mumbai
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/amoy-staging
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/sepolia-staging
 
 ### Production
 
 A `production` subgraph deployment to can be triggered through the GitHub UI by running the workflow `deploy-prod-subgraph.yaml`. For details have a look at [`.github/workflows/deploy-prod-subgraph.yaml`](../.github/workflows/deploy-prod-subgraph.yaml.). Access this subgraph via:
 
-- TODO
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/polygon
+- https://api.thegraph.com/subgraphs/name/bosonprotocol/ethereum
diff --git a/e2e/meta-tx-gateway/package.json b/e2e/meta-tx-gateway/package.json
@@ -1,6 +1,6 @@
 {
   "name": "meta-tx-gateway",
-  "version": "1.7.4",
+  "version": "1.7.5-alpha.0",
   "description": "",
   "main": "index.js",
   "private": true,
@@ -23,7 +23,7 @@
   },
   "homepage": "https://github.com/bosonprotocol/core-components#readme",
   "dependencies": {
-    "@bosonprotocol/common": "^1.27.0",
+    "@bosonprotocol/common": "^1.27.1-alpha.0",
     "cors": "^2.8.5",
     "dotenv": "^16.0.2",
     "ethers": "^5.7.0",