Skip to content

Commit

Permalink
revised verbiage in README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
dylan-bourque committed Jan 7, 2019
1 parent a08bb9b commit 2d35c48
Showing 1 changed file with 5 additions and 1 deletion.
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -61,7 +61,11 @@ Go 1.2+, but support for these older versions is not actively maintained.

## Go 1.11 Modules

At this time, this repository does not opt in to the experimental Go modules feature. Users who took a dependency on v3.1.1+ (where we _did_ temporarily enable support for modules) will need to modify their import paths to no longer use the `github.com/gofrs/uuid/v3` Semantic Import Version path. Please refer to [Issue #61](https://github.com/gofrs/uuid/issues/61) and [Issue #66](https://github.com/gofrs/uuid/issues/66) for more details.
As of v3.2.0, this repository no longer adopts Go modules, and v3.2.0 no longer has a `go.mod` file. As a result, v3.2.0 also drops support for the `github.com/gofrs/uuid/v3` import path. Only module-based consumers are impacted. With the v3.2.0 release, _all_ gofrs/uuid consumers should use the `github.com/gofrs/uuid` import path.

An existing module-based consumer will continue to be able to build using the `github.com/gofrs/uuid/v3` import path using any valid consumer `go.mod` that worked prior to the publishing of v3.2.0, but any module-based consumer should start using the `github.com/gofrs/uuid` import path when possible and _must_ use the `github.com/gofrs/uuid` import path prior to upgrading to v3.2.0.

Please refer to [Issue #61](https://github.com/gofrs/uuid/issues/61) and [Issue #66](https://github.com/gofrs/uuid/issues/66) for more details.

## Usage

Expand Down

0 comments on commit 2d35c48

Please sign in to comment.