Prepare release 0.31.0

[Ivansete-status]

Items to complete

All items below are to be completed by the owner of the given release.

Note that status.staging refers to shards.staging fleet.

• [x] Create release branch

• [x] Assign release candidate tag to the release branch HEAD. e.g. v0.30.0-rc.0

• [x] Generate and edit releases notes in CHANGELOG.md

• [x] End user impact: Summarize impact of changes on Status end users (can be a comment in this issue). These are all the changes: https://github.com/waku-org/nwaku/compare/v0.30.2...v0.31.0-rc.1 En user impact summary: The store-v3 requests can be performed correctly.

• [x] Validate release candidate

• [ ] Automated testing

  • [ ] Ensures js-waku tests are green against release candidate note: we could not validate that because there were issues in js-waku tests. This will get sorted out for next release.

  • [x] Ask Vac-QA and Vac-DST to perform available tests against release candidate

  • [ ] On Waku fleets

  • [x] Lock waku.test fleet to release candidate version

  • [ ] Continuously stress waku.test fleet for a week (e.g. from wakudev)

  • [x] Search Kibana logs from the previous month (since last release was deployed), for possible crashes or errors in waku.test and waku.sandbox.

    • Most relevant logs are (fleet: "waku.test" OR fleet: "waku.sandbox") AND message: "SIGSEGV"

  • [x] Run release candidate with waku-simulator, ensure that nodes connected to each other

  • [ ] Unlock waku.test to resume auto-deployment of latest master commit

  • [ ] On Status fleet

  • [x] Deploy release candidate to status.staging

  • [x] Perform sanity check and log results as comments in this issue.

    • [x] Connect 2 instances to status.staging fleet, one in relay mode, the other one in light client.
    • [x] 1:1 Chats with each other
    • [x] Send and receive messages in a community
    • [x] Close one instance, send messages with second instance, reopen first instance and confirm messages sent while offline are retrieved from store

  • [x] Perform checks based end user impact We validated that the following is working fine from Status-Desktop PoV: https://github.com/status-im/status-desktop/pull/15615

  • [x] Ask other (Waku and Status) CCs to point their instance to status.staging for a week and use the app as usual.

  • [x] Ask Status-QA to perform sanity checks (as described above) + checks based on end user impact; do specify the version being tested

  • [x] Ask Status-QA or infra to run the automated Status e2e tests against status.staging

  • [x] Get other CCs sign-off: they comment on this PR "used app for a week, no problem", or problem reported, resolved and new RC I've asked a few CC during some days but I didn't get much feedback.

  • [x] Get Status-QA sign-off. Ensuring that status.test update will not disturb ongoing activities.

• [ ] Proceed with release

  • [x] Assign a release tag to the same commit that contains the validated release-candidate tag
  • [x] Create GitHub release
  • [x] Deploy the release to DockerHub
  • [x] Announce the release

• [ ] Promote release to fleets.

  • [ ] Update infra config with any deprecated arguments or changed options
  • [ ] Deploy final release to waku.sandbox fleet
  • [x] Deploy final release to status.staging fleet
  • [x] Deploy final release to status.test fleet (soon to be status.prod)

• [ ] Post release

  • [ ] Submit a PR from the release branch to master. Important to commit the PR with "create a merge commit" option.
  • [x] Update waku-org/nwaku-compose with the new release version.

[Ivansete-status]

I tested this in status-staging fleet with v0.31.0-rc.1:

• Contact request
• Sending a few messages between two users
• Create a community and invite a contact
• Sign out user A. User B sends a few messages in the general community chat. The user A connects again and the app retrieves the messages sent while A was off.
• store-v3 tests with messages-finder app (with and without data.) https://github.com/waku-org/message-finder

[yevh-berdnyk]

Just checked nightly e2e test results - during the last 3 days only 2 tests failed with the of not received messages. Will update with the next results later

[churik]

test run is here: https://ethstatus.testrail.net/index.php?/runs/view/17327&group_by=cases:section_id&group_order=asc

There are no failures related to message reliability in this run.

Thank you @Ivansete-status for checking

[AlbertoSoutullo]

From DST, the simulations behave as expected. More information about this batch of simulations here: https://www.notion.so/2039-78aeac4f220a49ea97e780b7bb60c412

We will add more versions in the plot for the waku regression testing report.