Prepare for v0.14.4 release

Also update the release instructions to bump the version in RELEASE.md,
such that we can copy-paste `export RELEASE=v...` next time ;-)

Signed-off-by: Tobias Klauser <[email protected]>

README.md

@@ -43,7 +43,7 @@ binary releases.
 
 | Release                                                              | Maintained | Supported Cilium Versions |
 |----------------------------------------------------------------------|------------|---------------------------|
-| [v0.14.3](https://github.com/cilium/cilium-cli/releases/tag/v0.14.3) | Yes        | Cilium 1.11 and newer     |
+| [v0.14.4](https://github.com/cilium/cilium-cli/releases/tag/v0.14.4) | Yes        | Cilium 1.11 and newer     |
 | [v0.10.7](https://github.com/cilium/cilium-cli/releases/tag/v0.10.7) | No         | Cilium 1.10               |
 
 Please see [Experimental `helm` installation mode](#experimental-helm-installation-mode)

RELEASE.md

@@ -19,22 +19,21 @@ table](https://github.com/cilium/cilium-cli#releases) for the most recent suppor
 Set `RELEASE` environment variable to the new version. This variable will be
 used in the commands throughout the documenat to allow copy-pasting.
 
-For example, if you are releasing `v5.4.0`:
-
-    export RELEASE=v5.4.0
+    export RELEASE=v0.14.5
 
 ## Prepare the release
 
 ### Update the README.md
 
 Update the *Releases* section of the `README.md` which lists all currently
 supported releases in a table. The version in this table needs to be updated to
-match the new release `$RELEASE`.
+match the new release `$RELEASE`. Also bump `$RELEASE` in the section above, so
+it can be copy-pasted when preparing the next release.
 
 ### Create release preparation branch and open PR
 
     git checkout -b pr/prepare-$RELEASE
-    git add README.md
+    git add README.md RELEASE.md
     git commit -s -m "Prepare for $RELEASE release"
     git push origin HEAD