Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • network/gdev-800 protected
  • cgeek/issue-297-cpu
  • gdev-800-tests
  • update-docker-compose-rpc-squid-names
  • fix-252
  • 1000i100-test
  • hugo/tmp-0.9.1
  • network/gdev-803 protected
  • hugo/endpoint-gossip
  • network/gdev-802 protected
  • hugo/distance-precompute
  • network/gdev-900 protected
  • tuxmain/anonymous-tx
  • debug/podman
  • hugo/195-doc
  • hugo/195-graphql-schema
  • hugo-tmp-dockerfile-cache
  • release/client-800.2 protected
  • release/runtime-800 protected
  • gdev-900-0.10.1 protected
  • gdev-900-0.10.0 protected
  • gdev-900-0.9.2 protected
  • gdev-800-0.8.0 protected
  • gdev-900-0.9.1 protected
  • gdev-900-0.9.0 protected
  • gdev-803 protected
  • gdev-802 protected
  • runtime-801 protected
  • gdev-800 protected
  • runtime-800-bis protected
  • runtime-800 protected
  • runtime-800-backup protected
  • runtime-701 protected
  • runtime-700 protected
  • runtime-600 protected
  • runtime-500 protected
  • v0.4.1 protected
  • runtime-401 protected
  • v0.4.0 protected
40 results

release-new-runtime.md

Blame
    • Cédric Moreau's avatar
      918d5828
      runtime-800 updates (!240) · 918d5828
      Cédric Moreau authored 
      * update metadata

(and regenerate doc)

* release: documentation

* Revert "fix(#189): force rust-toolchain.toml for runtimes as well"

This reverts commit 86746b33.

* release: re-enable ARM build

* feat: client 0.8.0

* feat: client 0.8.0

* fix: Docker `--unsafe-ws-external` no more exist

* release: disable arm build

* release: runtime-800 gdev+gtest raw specs

* fix(#189): force rust-toolchain.toml for runtimes as well

* release: runtime-800 + spec update
      918d5828
      History
      runtime-800 updates (!240)
      Cédric Moreau authored 
      * update metadata

(and regenerate doc)

* release: documentation

* Revert "fix(#189): force rust-toolchain.toml for runtimes as well"

This reverts commit 86746b33.

* release: re-enable ARM build

* feat: client 0.8.0

* feat: client 0.8.0

* fix: Docker `--unsafe-ws-external` no more exist

* release: disable arm build

* release: runtime-800 gdev+gtest raw specs

* fix(#189): force rust-toolchain.toml for runtimes as well

* release: runtime-800 + spec update
    release-new-runtime.md 2.03 KiB

    Release a new Runtime

    The following instructions have been described in french at: Créer une release.

    Process

    Example for runtime-800.

    New release with new Runtime

    • create a release/runtime-800 branch locally
    • update the values:
      • update spec version (in runtime/<currency>/src/lib.rs)
      • eventually update gdev.yml (smiths, tech. committee, ...)
    • push the release/runtime-800 branch
      • in the CI/CD, wait for Create release button to be available and click on it (see above screenshot)

    The Runtime is now available on the release page runtime-800.

    New Client

    The Client is published as a Docker image.

    You may want to publish a new Client version along with a Runtime update.

    New raw specs (optional)

    For a reboot, you will likely want to update the raw specs:

    • in the CI/CD, wait for release_gdev_specs button to be available and click on it
    • in the CI/CD, wait for release_gtest_specs button to be available and click on it
    • wait for both jobs to finish
    • update the Client raw specs with cargo xtask update-raw-specs runtime-800

    New version (mandatory)

    Update Client values:

    • update Client version (in Cargo.toml)
    • update Cargo.lock with cargo build

    Publish Docker image

    Commit everything and push the branch:

    • in the CI/CD, a new pipeline has been launched
    • you can stop jobs create_g1_data, gdev_srtool, gtest_srtool (won't be used)
    • click on gdev_docker_deploy and gtest_docker_deploy

    The Docker images should now be available at: https://hub.docker.com/r/duniter/duniter-v2s-gdev/tags.

    Runtime tag and spec version

    Our runtime tags use xxyy version numbers where x corresponds to major change and y hotfix.

    Make sure to move any issue or merge request assigned to the choosen milestone runtime-xxyy to the next one. This prevents from forgetting unfinished work.