Update stable release to 1.16.4

Also update the release issue template to make the branch name unique
for each release.

Signed-off-by: Michi Mutsuzaki <[email protected]>

Author: michi-covalent

.github/ISSUE_TEMPLATE/release.md

@@ -94,11 +94,11 @@ title: 'vX.Y.Z release'
       release.
 - [ ] Update `stable.txt` in the main branch:
 
-      git switch -c pr/$USER/update-stable main
+      git switch -c pr/$USER/update-stable-to-$NEW_RELEASE main
       echo v$NEW_RELEASE > stable.txt
       git add README.md stable.txt
       git commit -s -m "Update stable release to $NEW_RELEASE"
-      git push origin pr/$USER/update-stable
+      git push origin pr/$USER/update-stable-to-$NEW_RELEASE
 
      and then open a pull request against the `main` branch, get it reviewed and merged.
 

README.md

@@ -72,7 +72,7 @@ this reason, only the latest Hubble CLI version is maintained.
 
 | Version                                              | Release Date         | Maintained | Supported Cilium Version | Artifacts                                                               |
 |------------------------------------------------------|----------------------|------------|--------------------------|-------------------------------------------------------------------------|
-| [v1.16](https://github.com/cilium/hubble/tree/main)  | 2024-10-28 (v0.16.3) | Yes        | Cilium 1.16 and older    | [GitHub Release](https://github.com/cilium/hubble/releases/tag/v1.16.3) |
+| [v1.16](https://github.com/cilium/hubble/tree/main)  | 2024-11-21 (v1.16.4) | Yes        | Cilium 1.16 and older    | [GitHub Release](https://github.com/cilium/hubble/releases/tag/v1.16.4) |
 
 ## Component Stability
 

stable.txt

@@ -1 +1 @@
-v1.16.3
+v1.16.4