Use correct release names in examples

README.md

@@ -234,7 +234,7 @@ The following workflows are available:
   Push a tag starting with `python-`, e.g., `python-v0.1.0`, to trigger a release of the Python implementation. The workflow will create a tarball of the `python/` directory and publish it as a release asset.
 
 - **Wireshark Plugin Release:**  
-  Push a tag starting with `wireshark-`, e.g., `wireshark-v2025.09.03`, to trigger a release of the Wireshark plugin binaries for all supported platforms.
+  Push a tag starting with `wireshark-`, e.g., `wireshark-v0.1.1`, to trigger a release of the Wireshark plugin binaries for all supported platforms.
 
 - **Zeek Release:**  
   Push a tag that is a pure semantic version (e.g., `v1.2.3`), with no prefix, to trigger a Zeek release. This will automatically create a release on [packages.zeek.org](https://packages.zeek.org/).
@@ -244,7 +244,7 @@ The following workflows are available:
 1. Ensure your changes are merged into the `main` branch.
 
 2. Create and push a tag for the component you want to release:
-   - For Rust, Python, or Wireshark, use the appropriate prefix (e.g., `rust-v0.18.5`, `python-v0.1.0`, `wireshark-v2025.09.03`).
+   - For Rust, Python, or Wireshark, use the appropriate prefix (e.g., `rust-v0.18.5`, `python-v0.1.0`, `wireshark-v0.1.1`).
    - For Zeek, use a pure semver tag (e.g., `v1.2.3`).
 
    Example:

wireshark/README.md

@@ -273,8 +273,8 @@ pytest
 To create a Wireshark plugin release, push a tag starting with `wireshark-`, for example:
 
 ```sh
-git tag wireshark-v2025.09.03
-git push origin wireshark-v2025.09.03
+git tag wireshark-v0.1.1
+git push origin wireshark-v0.1.1
 ```
 
 ## License