From ac96d590e3a623fddb9b049906dbb01d0aa1624c Mon Sep 17 00:00:00 2001
From: thepudds <20628140+thepudds@users.noreply.github.com>
Date: Tue, 8 Jan 2019 10:20:50 -0500
Subject: [PATCH] provide additional semver example with a prerelease tag

---
 Modules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Modules.md b/Modules.md
index cfb0ee55..1b5da97c 100644
--- a/Modules.md
+++ b/Modules.md
@@ -153,7 +153,7 @@ Summarizing the relationship between repositories, modules, and packages:
 * Each module contains one or more Go packages.
 * Each package consists of one or more Go source files in a single directory.
 
-Modules must be semantically versioned according to [semver](https://semver.org/) in the form `v(major).(minor).(patch)`, such as  `v0.1.0` or `v1.2.3`. The leading `v` is required. If using Git, [tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) released commits with their versions. Public and private module repositories and proxies are becoming available (see FAQ [below](https://github.com/golang/go/wiki/Modules#are-there-always-on-module-repositories-and-enterprise-proxies)).
+Modules must be semantically versioned according to [semver](https://semver.org/) in the form `v(major).(minor).(patch)`, such as  `v0.1.0`, `v1.2.3`, or `v1.5.0-rc.1`. The leading `v` is required. If using Git, [tag](https://git-scm.com/book/en/v2/Git-Basics-Tagging) released commits with their versions. Public and private module repositories and proxies are becoming available (see FAQ [below](https://github.com/golang/go/wiki/Modules#are-there-always-on-module-repositories-and-enterprise-proxies)).
 
 ### go.mod