anchor.diff:  . Test the recipe locally, including installing from the bottle: `brew reinstall --force-bottle aktualizr`.
   . Open a PR on the https://github.com/advancedtelematic/homebrew-otaconnect[homebrew-otaconnect] repo to update the recipe with all your changes.
   
  -== Test the released Debian packages
  +== Verify the released Debian packages
   
  -Don't forget to test the resulting Debian packages manually!
  +Newly created releases automatically trigger an OTF pipeline in gitlab. Currently, you still need to manually verify that the pipeline actually succeeded.
  +
  +== Update meta-updater
  +
  +The version of aktualizr used by link:https://github.com/advancedtelematic/meta-updater/[meta-updater] should be updated to match the new release. First, open a PR against master that updates aktualizr to the same commit used in the newly released tag. This is also a good time to update the aktualizr recipe to pull the latest version of link:https://ats-tuf-cli-releases.s3-eu-central-1.amazonaws.com/index.html[garage-sign].
  +
  +Once that PR has passed oe-selftest, successfully passed review, and gotten merged, you should then backport that change, along with anything else relevant since the last backport was done, to the xref:yocto-release-branches.adoc[currently supported release branches]. Note that while master is allowed to use arbitrary recent version of aktualizr, the release branches should only use released versions of aktualizr.
  
positive.code: 
  Gitlab will build this tag and automatically create a release for it on github.
  
  === Create a new docs branch
  
  Create (and push to github) a new branch with the commit you just tagged as the parent:
  
  
negative.code: 
  == Update doxygen on github
  
  You will need to update the link:https://advancedtelematic.github.io/aktualizr/index.html[doxygen documentation] both for the new release and master.
  
  === Add doxygen pages for the new release on github
  
  To add doxygen docs for a new tag, you will need to do something like the following:
  
  1. If you haven't already, check out the <<3-create-a-new-tag,newly created tag>> (`git checkout 2018.63`, for example).
  1. Create a clean build directory (to prevent using stale objects), then run CMake and doxygen again:
  +
  ----
  rm -rf build/*
  