waku-org/nwaku
1
0
Fork 0
mirror of https://github.com/waku-org/nwaku.git synced 2025-02-04 19:14:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

chore: adding nwaku compose image update to release process (#2370)

Browse Source
This commit is contained in:
gabrielmer 2024-01-26 11:00:03 +01:00 committed by GitHub
parent 025c6ec92a
commit 4f06dcffce
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 2 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/contributors/release-process.md
View File

@ -78,7 +78,8 @@ Ensure all items in this list are ticked:
> - `IMAGE_NAME`: `wakuorg/nwaku` > - `IMAGE_NAME`: `wakuorg/nwaku`
> - `NIMFLAGS`: `--colors:off -d:disableMarchNative -d:chronicles_colors:none -d:postgres` > - `NIMFLAGS`: `--colors:off -d:disableMarchNative -d:chronicles_colors:none -d:postgres`
> - `GIT_REF` the release tag (e.g. `v0.16.0`) > - `GIT_REF` the release tag (e.g. `v0.16.0`)
3. Deploy the release to appropriate fleets: 3. Update the default nwaku image in [nwaku-compose](https://github.com/waku-org/nwaku-compose/blob/master/docker-compose.yml)
4. Deploy the release to appropriate fleets:
- Inform clients - Inform clients
> **NOTE:** known clients are currently using some version of js-waku, go-waku, nwaku or waku-rs. > **NOTE:** known clients are currently using some version of js-waku, go-waku, nwaku or waku-rs.
> Clients are reachable via the corresponding channels on the Vac Discord server. > Clients are reachable via the corresponding channels on the Vac Discord server.