Merge pull request #2340 from daostack/release

Release 1.0.4

.storybook/webpack.config.js

@@ -26,6 +26,7 @@ module.exports = ({ config }) => {
     reducers: path.resolve(basePath, 'src/reducers'),
     selectors: path.resolve(basePath, 'src/selectors'),
     src: path.resolve(basePath, 'src'),
+    data: path.resolve(basePath, 'data'),
     'ipfs-api': 'ipfs-api/dist',
   };
   return config;

.travis/branch.yml

@@ -1,5 +1,5 @@
 language: node_js
-node_js: 12.18.4
+node_js: 12.20.0
 addons:
   apt:
     update: true

.travis/pr.yml

@@ -1,5 +1,5 @@
 language: node_js
-node_js: 12.18.4
+node_js: 12.20.0
 addons:
   apt:
     update: true

CHANGELOG.md

@@ -1,3 +1,22 @@
+## 1.0.4
+  - Features Added
+    - Brand new Proposals Page
+
+  - Improvements
+    - Verify parameters hash
+    - Whitelist PrimeDAO Token
+    - Use subgraph v41_4 and arc.js 0.2.80
+    - Some UI/UX improvements
+    - Alchemy 2.0 banners are removed
+
+  - Bugs Fixed
+    - Execute Calls button is displayed in Generic Scheme proposal before it passed
+    - Issue connecting to WalletConnect
+    - Can't create multi-call proposal in some cases due to old migration version
+
+  - Features Removed
+    - Dao History Page
+
 ## 1.0.3
   - Features Added
     - Support multiple networks

data/tokens.json

@@ -83,6 +83,11 @@
         "name": "Panvala pan",
         "symbol": "PAN"
       }
+    },
+    "0xe59064a8185ed1fca1d17999621efedfab4425c9": {
+      "decimals": 18,
+      "name": "PrimeDAO Token",
+      "symbol": "PRIME"
     }
   },
   "rinkeby": {

docker-compose.yml

@@ -47,18 +47,18 @@ services:
       GRAPH_MAX_IPFS_FILE_BYTES: 900000
 
   ipfs:
-    image: daostack/test-env-ipfs:3.0.41
+    image: daostack/test-env-ipfs:3.0.42
     ports:
       - 5001:5001
 
   postgres:
-    image: daostack/test-env-postgres:3.0.41
+    image: daostack/test-env-postgres:3.0.42
     ports:
       - 9432:5432
     environment:
       POSTGRES_PASSWORD: 'letmein'
 
   ganache:
-    image: daostack/test-env-ganache:3.0.41
+    image: daostack/test-env-ganache:3.0.42
     ports:
       - 8545:8545

docs/fetchingandsubscribingdata.md

@@ -14,7 +14,7 @@ Executing these four steps for each React component is quite expensive (just thi
 So the approach we are taking in Alchemy is the following.
 
 *to avoid the cost of step 2.:*
-Fetch the data that is used by many subcomponents in a single query, before those components are rendered. When those subcomponents are rendered, they will be able to get their data directly  from the cache, and so will avoid a server request in step 2. An example of that pattern is found in the `DaoHistoryPage.tsx`
+Fetch the data that is used by many subcomponents in a single query, before those components are rendered. When those subcomponents are rendered, they will be able to get their data directly  from the cache, and so will avoid a server request in step 2.
 
 *To avoid the cost of step 4:*
 The line `arcSettings.graphqlSubscribeToQueries = false;` overrides arc.js default behavior to open a subscription for each query. So, by default, step 4 is skipped. Instead, we insert, in strategic places, subscriptions to relatively big queries, that will update the cache only for the data that we need.