bump amps

Author: gionn

.github/updatecli/updatecli_maven_v23_values.yml

@@ -1,3 +1,3 @@
 updatecli_matrix_version: 23.N
-updatecli_amps_release_branch: "release/23.N"
+updatecli_amps_release_branch: "release/23.5"
 ansible_version_file: vars/acs23.yml

.github/updatecli/updatecli_maven_v25_values.yml

@@ -1,5 +1,5 @@
 updatecli_matrix_version: current
-updatecli_amps_release_branch: "release/25.1"
+updatecli_amps_release_branch: "release/25.2"
 ansible_version_file: vars/acs25.yml
 artifacts:
   alfresco-googledrive-repo-community:

.github/updatecli/updatecli_maven_v73_values.yml

@@ -1,5 +1,5 @@
 updatecli_matrix_version: 7.3.N
-updatecli_amps_release_branch: "release/7.3.N"
+updatecli_amps_release_branch: "release/7.3.2"
 ansible_version_file: vars/acs73.yml
 artifacts:
   alfresco-audit-storage:

.github/updatecli/updatecli_maven_v74_values.yml

@@ -1,5 +1,5 @@
 updatecli_matrix_version: 7.4.N
-updatecli_amps_release_branch: "release/7.4.N"
+updatecli_amps_release_branch: "release/7.4.2"
 ansible_version_file: vars/acs74.yml
 artifacts:
   alfresco-audit-storage:

README.md

@@ -221,19 +221,21 @@ Follow the checklist:
    against an existing branch to push bumps there or against `master` to push
    the bumps to `updatecli-bump-versions` branch.
 6. Manually bump adw and acc which are not yet supported by updatecli.
-7. Ensure that the [versions table in the main readme](docs/overview.md#versioning) has been updated
-8. Ensure that docker images and AMI id for the root molecule tests are
+7. Ensure that `updatecli_amps_release_branch` in the different
+   `updatecli_maven_*.yml` files is set to the current branch.
+8. Ensure that the [versions table in the main readme](docs/overview.md#versioning) has been updated
+9. Ensure that docker images and AMI id for the root molecule tests are
    reflecting any minor OS release (e.g. [default suite](../molecule/default/))
-9. Ensure that activemq, tomcat and java versions are up to date (latest patch
+10. Ensure that activemq, tomcat and java versions are up to date (latest patch
    version) If activemq needs minor bump for latest release bump also the version in
    `prepare.yml` molecule scenario for multimachine.
-10. After merging every pending PR, proceed with tagging:
+11. After merging every pending PR, proceed with tagging:
     * `git tag -s v2.x.x -m v2.x.x`
     * `git push origin v2.x.x`
-11. Wait for the [Release
+12. Wait for the [Release
   workflow](https://github.com/Alfresco/alfresco-ansible-deployment/actions/workflows/release.yml)
   go green.
-12. [Draft a new
+13. [Draft a new
   release](https://github.com/Alfresco/alfresco-ansible-deployment/releases) on
   GitHub with the tag you just pushed. If the release is for a new ACS major
   version, mention the ACS release in the title, e.g. v2.x.x (ACS 23.4.0)