Release v2024 12 20

Prepare the release process

• Made a copy of the latest release Release-v2024-11-18 documented as a new page on cardano-wallet's wiki called Release-v2024-12-20.

• Pick up the latest green commit from the release pipeline and prove it's green by linking the successful buildkite and github actions builds here.

  • master branching point:

  • release commit:

  • relelase pipeline build:

  • main pipeline build:

  • Check Windows E2E tests on release commit artifacts, note that the github action code is taken from master

  • [ ] Check Windows unit tests on release commit artifacts

  • Check for performance regressions on the release commit artifacts:

  • Unblock the release block on relelase pipeline build

Update the release page

• Fix the release note on the draft release automatically created by the release pipeline https://github.com/cardano-foundation/cardano-wallet/releases

Check out the docker image is on the docker hub

• link: https://hub.docker.com/r/cardanofoundation/cardano-wallet/tags
• Report the link in the release notes

Check out the bump.sh portal has the new release

• https://bump.sh/hal-cardano-foundation/doc/cardano-wallet-backend

Fix redirect links in the documentation

• Make a commit with redirects to the documentation for the release like

  ```bash
  git clone [email protected]:cardano-foundation/cardano-wallet.git
  cd cardano-wallet
  export NEW_GIT_TAG=v2024-12-20
  git checkout gh-pages
  git pull origin gh-pages
  cd releases
  ./make_redirects.sh $NEW_GIT_TAG
  git push origin gh-pages
  ```
  A ticket is opened to automate this step
  https://cardanofoundation.atlassian.net/browse/ADP-3428
  

Check sensitive fields in the API

• Verify that sensitive fields listed in Cardano/Wallet/Api/Server are still accurate and aren't missing any new ones.

  sensitive =
      [ "passphrase"
      , "old_passphrase"
      , "new_passphrase"
      , "mnemonic_sentence"
      , "mnemonic_second_factor"
      ]
  

Publication

• Once two engineers have signed off, publish the release draft.

• Merge the (administrative) commits created for the release tag back into the master branch.

• Check out the documentation has been published by the github action

• Remember to leave this checklist in an up-to-date status for the next releaser