github-actions[bot]
commented
6 months ago size-limit report 📦
| Path | Size | Loading time (3g) | Running time (snapdragon) | Total time |
|---|---|---|---|---|
| Waku node | 180.85 KB (0%) | 3.7 s (0%) | 3.5 s (+52.2% 🔺) | 7.1 s |
| Waku Simple Light Node | 180.73 KB (0%) | 3.7 s (0%) | 2.3 s (-6.98% 🔽) | 5.9 s |
| ECIES encryption | 23.11 KB (0%) | 463 ms (0%) | 640 ms (+25.97% 🔺) | 1.2 s |
| Symmetric encryption | 22.58 KB (0%) | 452 ms (0%) | 550 ms (-1.11% 🔽) | 1.1 s |
| DNS discovery | 72.4 KB (0%) | 1.5 s (0%) | 1.8 s (+65.2% 🔺) | 3.2 s |
| Peer Exchange discovery | 73.97 KB (0%) | 1.5 s (0%) | 1.6 s (+18.2% 🔺) | 3 s |
| Local Peer Cache Discovery | 67.71 KB (0%) | 1.4 s (0%) | 1.7 s (+47.11% 🔺) | 3 s |
| Privacy preserving protocols | 38.75 KB (0%) | 775 ms (0%) | 649 ms (-44.31% 🔽) | 1.5 s |
| Waku Filter | 20.17 KB (0%) | 404 ms (0%) | 567 ms (+24.27% 🔺) | 970 ms |
| Waku LightPush | 110.12 KB (0%) | 2.3 s (0%) | 1.5 s (+0.08% 🔺) | 3.8 s |
| History retrieval protocols | 110.62 KB (0%) | 2.3 s (0%) | 2.1 s (+35.33% 🔺) | 4.3 s |
| Deterministic Message Hashing | 4.83 KB (0%) | 97 ms (0%) | 110 ms (+454.68% 🔺) | 206 ms |
Problem
Since
discoveryis consumed and locked to 0.0.1 in other packages and release bot tries to bump it to 0.0.2 - it fails.Solution
We should seed release with 0.0.0 to have 0.0.1 as the first version to be released. According to docs it seems the most straightforward way