File tree 1 file changed +3
-3
lines changed
1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -87,15 +87,15 @@ Once the node template is running locally, you can connect to it with frontends
87
87
here is actually not important: since Substrate uses git references for its Substrate
88
88
dependencies it means that once one package is updated all are.
89
89
- [ ] Increment the minor version number in ` node/Cargo.toml ` and ` runtime/Cargo.toml ` .
90
- - [ ] Execute ` cargo run --release -- --tmp ` . If successful, it should produce blocks
90
+ - [ ] Execute ` cargo run --release ` . If successful, it should produce blocks
91
91
and a new, up to date, ` Cargo.lock ` will be created.
92
92
- [ ] Update this readme with the hash of the Substrate ` master ` commit
93
93
with which you synchronized. The hash appears two times in this
94
- readme.
94
+ readme.
95
95
- [ ] Create a PR with the changes, have it reviewed and merged.
96
96
- [ ] Replace ` XX ` in this command with your incremeted version number and execute it:
97
97
` git checkout main && git pull && git tag v0.XX.0 && git push origin v0.XX.0 ` .
98
- This will push a new tag with the version number to this repository.
98
+ This will push a new tag with the version number to this repository.
99
99
- [ ] We have set this repository up in a way that tags à la ` vX.X.X ` trigger
100
100
a CI run that creates a GitHub draft release. You can observe CI runs on
101
101
[ GitLab] ( https://gitlab.parity.io/parity/mirrors/substrate-contracts-node/-/pipelines ) .
You can’t perform that action at this time.
0 commit comments