anchor.diff:  . Edit any links found in the `README.adoc`, located in the root of the repository, that are versioned, so they match the version value you just set in the `antora.yml` file.
   . Add `./.cache/antora/*` back to the  `Commit Packages` command to rebuild the cache.
   . Stage, commit and push the changes to the repository.
  +. Navigate to the Docsearch config repo and update the search script.
  ++
  +https://github.com/algolia/docsearch-configs
  +
  +.. From the main page, click the btn:[Go to file] button and Enter `jmonkeyengine` into the search line.
  +
  +.. Edit the version line to point to the new version used in the `Antora.yml` file. In this example, search is targeting v3.3.
  ++
  +--
  +.Old jmonkeyengine.json
  +[source, .json]
  +----
  +{
  +  "index_name": "jmonkeyengine",
  +  "start_urls": [
  +    {
  +      "url": "https://wiki.jmonkeyengine.org/docs/(?P<version>.*?)/",
  +      "variables": {
  +        "version": [
  +          "3.3"
  +        ]
  +      }
  +    }
  +  ],
  +
  +  ...
  +}
  +----
  +
  +and the master branch `Antora.yml` file is using v3.4.
  +
  +.Antora.yml
  +[source, yml]
  +----
  + name: docs
  + title: JME
  + version: '3.4'
  +
  +...
  +----
  +
  +.Updated jmonkeyengine.json
  +[source, .json]
  +----
  +{
  +  "index_name": "jmonkeyengine",
  +  "start_urls": [
  +    {
  +      "url": "https://wiki.jmonkeyengine.org/docs/(?P<version>.*?)/",
  +      "variables": {
  +        "version": [
  +          "3.4"
  +        ]
  +      }
  +    }
  +  ],
  +
  +  ...
  +}
  +----
  +--
   
   Things to know about versions and component modules.
   
  
positive.code: ```
  name: docs-wiki
  title: Wiki Contribution
  version: '3.3'
  ```
  
  NOTE: The version value is enclosed in a set of single quote marks (') because it starts with a number. As was mentioned earlier, the versioning is controlled by the antora.yml file, not the playbook, so they do not have to match.
  
negative.code: ```
  . Next, delete the `.cache` folder.
  . Stage, commit and push your changes to the repository.
  . Create a new branch that matches the *current version* of the wiki. If master is currently targeting 3.4 for example, that would mean the branch name would be v3.3.
  . Push the branch to the repository.
  . On the `master` branch, edit these files:
  .. Add the newly created branch to the `branches:` array in wiki-playbook.yml.
  