Release v1 - Albula

[vimukthi-git]

Release v1

• If it is the first release of the v<Major> (eg: v5) line then create a branch release-v<Major>. Execute the following steps on that branch.
• Generate weights, i.e run benchmark
• Runtime versioning updates
  • Update spec_version (automate-able)
• Update composable node version if the code has changed
• Update composableJs version (if necessary to be released)
• Update FE version (if necessary to be released)
• Update Subsquid version (if necessary to be released)
• Update relevant frame pallets being released in runtimes to the latest node version
• Consider and list possible proxy filter updates for available calls.
• Categorize (and give a title) the release according to the types of changes it does, eg: security patch, bugfix, feature etc.
• Run cargo build once to update the Cargo.lock file.
• Update the v<Major> branch on Github and make PR to master. Get it merged to main before next step. Note that v<Major> branch must not be deleted.
• Get the tip of the branch signed according to 3.2.4 section.
• Finally, create a tag v<Branch.Spec_version> (eg: v5.4201) to trigger the release artifact build.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
pablo-nightly	✅ Ready (Inspect)	Visit Preview	Nov 24, 2022 at 0:37AM (UTC)
pablo-staging	✅ Ready (Inspect)	Visit Preview	Nov 24, 2022 at 0:37AM (UTC)
picasso-nightly	✅ Ready (Inspect)	Visit Preview	Nov 24, 2022 at 0:37AM (UTC)

[github-actions]

Nix commands for this PR

NOTE: You can also run our Nix commands in Docker. See the bottom of this comment.

Make sure you have setup the Composable community cache:

(you only need to run it once on your machine)

nix-shell -p cachix --command "cachix use composable-community"

Show all possible apps, shells and packages:

nix flake show "github:ComposableFi/composable/66935bdfb2398e70211606b5b35a018122a439bb --allow-import-from-derivation

Run the Composable node alone:

nix run "github:ComposableFi/composable/66935bdfb2398e70211606b5b35a018122a439bb#composable-node" -L

Spin up a local devnet:

nix run "github:ComposableFi/composable/66935bdfb2398e70211606b5b35a018122a439bb#devnet" -L --option sandbox relaxed --show-trace

Spin up a local XCVM devnet:

nix run "github:ComposableFi/composable/66935bdfb2398e70211606b5b35a018122a439bb#devnet-xcvm" -L

View the docs:

nix run ".#docs-server"

Run this without Nix in Docker.

docker run --rm -v /var/run/docker.sock:/var/run/docker.sock -v nix:/nix -it nixos/nix bash -c "nix-env -iA nixpkgs.cachix && cachix use composable-community && nix run github:ComposableFi/Composable/66935bdfb2398e70211606b5b35a018122a439bb#devnet-dali -L --extra-experimental-features nix-command --extra-experimental-features flakes"

NOTE: You can swap devnet-dali in the command above with any Nix package

For more info on how to use Nix, check out our Nix docs

Note that the initial build may take about one hour if it has not been cached by our CI yet. Once it is cached, builds should take about one minute. We currently do not provide build caches for ARM machines such as M1 Macs, but building on ARM is supported.

[hussein-aitlahcen]

Was not aware of such limitation, lol:

error: Minor version needs to fit into `u8`
  --> parachain/frame/crowdloan-rewards/src/lib.rs:69:1

[vimukthi-git]

Yeah I'm trying to fix that up by not using the same release minor version for the runtime code modules :D

[github-actions]

Visit the preview URL for this PR (updated for commit 66935bd):

https://picasso-f0d16--pr2263-release-v1-5e2h6krm.web.app

_{(expires Thu, 01 Dec 2022 01:18:02 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: d4e030ec330173845b1768cd217beee9791d20f1}

[github-actions]

Visit the preview URL for this PR (updated for commit 66935bd):

https://pablo-afa5d--pr2263-release-v1-40ec0oed.web.app

_{(expires Thu, 01 Dec 2022 01:18:21 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 8ef316967fc7aa470dc109d617260c43c009e4e3}

[benluelo]

should all of the packages in the repo be at 1.0.0? currently we have this:

1.10001.0:

• subsquid: https://github.com/ComposableFi/composable/pull/2263/files#diff-dc12ff78bbe9a7931b1c14d403fa4f25618e2dd587f5a2ea22454dc133f400deR3
• composablejs: https://github.com/ComposableFi/composable/pull/2263/files#diff-f8da4f783418bd85241431283a64ffbd4a2078ea450b47e969a2b40a195e1ac1R3
• root Cargo.toml: https://github.com/ComposableFi/composable/pull/2263/files#diff-f125ae0d47d8c963fc28b491bea921249d2c3375dcfdfe4443d05b222227c45aR6

1.0.1:

• frontend: https://github.com/ComposableFi/composable/pull/2263/files#diff-da6498268e99511d9ba0df3c13e439d10556a812881c9d03955b2ef7c6c1c655R3

and all of the other Cargo.toml files appear to be on 1.0.0. 1.10001.0 isn't exactly semver, so not using it in most places makes sense. mostly curious about frontend being at 1.0.1

[vimukthi-git]

@benluelo We allow individual packages to follow different schemes for versions refer RFC-0011 for details