commit e0de7f9288c498e931539c019b8abf03c9d11ca3
parent 21fbc828636f8e23d5c5423a968d2c0f959844f5
Author: Jack Mordaunt <jackmordaunt.dev@gmail.com>
Date: Fri, 18 Sep 2026 13:17:16 -0400
go.mod: retract v1.0.0
v1.0.0 was tagged and pushed while the API was still moving. It exposed
the package-level Start, End, Load, Decode and Play that a Decoder value
has since replaced, and it decoded 24-bit sources to 24-bit rather than
the s16le the package documents.
The proxy has that version cached, so its content cannot be changed.
Retracting is the mechanism Go provides instead: go get stops selecting
it and anyone already on it is told to move. pkg.go.dev reports no
importers, so this costs nobody anything.
The next tag takes over the v1 line rather than moving to v2. Removing
exported functions inside a major version is a semver violation, and
with no dependents it protects nobody while welding a /v2 suffix onto
every import path forever.
Diffstat:
1 file changed, 6 insertions(+), 0 deletions(-)
diff --git a/go.mod b/go.mod
@@ -8,3 +8,9 @@ require (
)
require github.com/ebitengine/purego v0.7.1 // indirect
+
+// v1.0.0 went out before the API had settled. It still exposed the
+// package-level Start, End, Load, Decode and Play that v1.1.0 replaces
+// with a Decoder value, and it decoded 24-bit sources to 24-bit rather
+// than the s16le the package documents. Nothing depended on it.
+retract v1.0.0
