anchor.diff:  
   Gitlab will build this tag and automatically create a release for it on github.
   
  -=== Create a new docs branch
  +=== Updating an already-released tag
  +
  +Generally, you should not update a tag after it has already been pushed to github. This is asking for confusion and problems down the line. However, if something goes wrong in creating the release from the tag, you may need to do this anyway. Note that you will need to manually delete the release on github if it has been created already. (Otherwise, the release's files will not get updated.) You will then need to either retry the specific github-release step or re-trigger the entire pipeline (which can be done by re-pushing the tag to github).
  +
  +== Create a new docs branch
   
   Create (and push to github) a new branch with the commit you just tagged as the parent:
   
  
positive.code: 1. In the second repo, make a directory for the tag or commit you wish to add, i.e. `mkdir 2018.63`.
  1. Copy the contents of `<build_dir>/docs/doxygen/html` into the directory you just created. (Something like `cp -a <build_dir>/docs/doxygen/html/* <second_repo>/2018.63`.)
  1. In the second repo, run `git add 2018.63`, `git commit -as`, and `git push`.
  1. Wait a minute or two for github to refresh and render the files.
  
  == Update the description of the github release
  
negative.code: . 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.
  
  == Verify the released Debian packages
  
  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.
  