mirror of
https://github.com/amnezia-vpn/amneziawg-go.git
synced 2026-10-14 05:41:54 +00:00
[GH-ISSUE #139] v1.x.x versions from go.dev and semver oddities #75
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
amnezia-vpn/amneziawg-go#75
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qdm12 on GitHub (May 21, 2026).
Original GitHub issue: https://github.com/amnezia-vpn/amneziawg-go/issues/139
Originally assigned to: @ygurov on GitHub.
On go.dev it looks like you have a few 1.x.x versions: https://pkg.go.dev/github.com/amnezia-vpn/amneziawg-go?tab=versions released last summer 2025. The problem is this triggers dependabot to update from v0.2.x to v1.x.x although it seems these v1.x.x are not even in the repository. Would be nice if you can figure out how to delete these v1.x.x tags from go.dev 😉 Thanks!
@ygurov commented on GitHub (Jun 17, 2026):
Hi @qdm12 @stereomonk
Yep, we cannot force anything on the go caching side to remove the packages, unfortunately
The reason we did not make a new major version yet is simple: a lot of wrappers do use it and the change will require the import renaming job all over the projects.
Assigning myself to the issue, but I am not really sure how fast we can resolve it
@qdm12 commented on GitHub (Jun 18, 2026):
I would say to just keep it opened for visibility for other users of this package. Also be careful whenever you do release a v1 of the package it will likely conflict with the existing bad v1 tags out there already
@qdm12 commented on GitHub (Sep 29, 2026):
Resolved with new v3.x.y tags