anchor.diff:  to e.g.
   +
   [source,java]
  -private final static String CAMEL_VERSION = "3.12.x";
  +private final static String CAMEL_VERSION = "3.13.x";
   
   At this point, build each project (`mvn clean install -Pfastinstall`) and check for generated changes that should be committed.
   
   NOTE: TODO: Is there a step of setting up CI or the regen bot?
   Should maven snapshots be deployed?
  +
  +=== Changes to other subprojects
  +
  +Be sure the subprojects using the latest release of main camel are aware that they need to update to the latest version, including documentation updates.
  +Any reference to the main camel documentation should use a version set in the subproject antora.yml component descriptor(s).
  +This may be set automatically from another source such as a maven `pom.xml`.
  +
  +Subproject changes are likely to involve code as well as documentation changes and need to be done by a subproject expert.
  +This section only attempts to describe the documentation changes needed.
   
   In the `camel-quarkus` project examine the root `pom.xml` of every version used in the website.
   There will be a property entry like:
  
positive.code: 
  === Changes to the Antora playbook
  
  NOTE: After a release, consider whether any LTS versions are now out of service and should be removed from the documentation.
  
  There are two cases to consider in modifying `camel-website:antora-playbook.yml`.
  
  New LTS version::
  Release after a non-LTS release::
  * Change the branch of the last release to that of the new release in the sources sections for camel, camel-karaf, and camel-spring-boot.
  Branches should be listed in reverse release order, newest first, preceded by the `main` prerelease branch.
  
  First release after an LTS release::
  * Add a new branch in the sources sections for camel, camel-karaf, and camel-spring-boot between `main` and the last LTS release branch.
  
  === Test your work!
  
  Create branches for each changed branch, push them, use those branches in your playbook, commit the playbook in a branch and push it, and open a PR for the playbook to find out if you missed anything.
  Wait for the PR build and netlify preview and check that the build succeeded and the preview looks good.
  
negative.code: In `camel-spring-boot/docs/components/antora.yml`::
  In `camel-spring-boot/docs/spring-boot/antora.yml`::
  
  * Change `version` to the branch name e.g. `3.13.x`
  * Remove the `prerelease` flag line
  * If the new branch is LTS, set the display-version to e.g. `3.13.x (LTS)`.
  * If the new branch is not LTS, remove the `display-version` line.
  
  In `camel-karaf:tooling/camel-karaf-docs-maven-plugin/src/main/java/org/apache/camel/karaf/maven/ExtMvelHelper.java`::
  