Shorten date in recommended pseudo version string (#4089)
Large integers in version strings can cause some older Bazel releases to
crash with a NumberFormatException.
diff --git a/docs/README.md b/docs/README.md
index 1c21528..f97521a 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -211,7 +211,7 @@
### Pseudo-versions
-If upstream hasn't released a new version in a long time (for example, due to project owner inactivity), but you'd still like to submit a version based on a main branch commit, the convention is to use a [pseudo-version](https://go.dev/ref/mod#pseudo-versions) similar to the one in the Go module system. Unlike in Go, such pseudo-versions are not semantically significant; they're just treated normally as any other version string. For example, if `foo`'s current version is `1.19.0`, you can submit a new version `1.19.1-20250305180549-abcdef`. This can also be combined with the `.bcr.<N>` suffix if necessary.
+If upstream hasn't released a new version in a long time (for example, due to project owner inactivity), but you'd still like to submit a version based on a main branch commit, the convention is to use a [pseudo-version](https://go.dev/ref/mod#pseudo-versions) similar to the one in the Go module system. Unlike in Go, such pseudo-versions are not semantically significant; they're just treated normally as any other version string. For example, if `foo`'s current version is `1.19.0`, you can submit a new version `1.19.1-20250305-abcdef`. This can also be combined with the `.bcr.<N>` suffix if necessary.
### Yank a module version
