Update README.md to use new 1.2.3 tag as example

Author: anthonyfok

README.md

@@ -42,17 +42,17 @@ Not recommend to use the `edge` version in python/Dockerfile of OpenDRR/opendrr-
 ## Creating ghcr.io/opendrr/python-env:latest production releases
 
 1. Create a new release tag,
-   e.g. a signed tag from the command-line by using `git tag -s v1.2.2`,
-   typing up a brief release notes, and `git push origin v1.2.2`. (optional)
+   e.g. a signed tag from the command-line by using `git tag -s v1.2.3`,
+   typing up a brief release notes, and `git push origin v1.2.3`. (optional)
 2. Alternatively or additionally, [draft a new release](https://github.com/OpenDRR/python-env/releases/new)
    through the GitHub web interface so the new release and release notes are immediately visible.
 3. Visit <https://github.com/OpenDRR/python-env/pkgs/container/python-env>
-   and check under "Recent tagged image versions" that the a new image versioned `latest` `1.2.2` is published.
+   and check under "Recent tagged image versions" that the a new image versioned `latest` `1.2.3` is published.
 
 To test locally:
 
 ```console
-docker run -it --rm ghcr.io/opendrr/python-env:1.2.2
+docker run -it --rm ghcr.io/opendrr/python-env:1.2.3
 ```
 
-To test with OpenDRR/opendrr-api, edit the `FROM` line in python/Dockerfile accordingly, e.g. `FROM ghcr.io/opendrr/python-env:1.2.2`.
+To test with OpenDRR/opendrr-api, edit the `FROM` line in python/Dockerfile accordingly, e.g. `FROM ghcr.io/opendrr/python-env:1.2.3`.