Skip to content

fix: retract v0.1.0 - #23

Merged
jaisonerick merged 1 commit into
mainfrom
fix/retract-v0.1.0
Apr 22, 2026
Merged

jaisonerick merged 1 commit into
mainfrom
fix/retract-v0.1.0

Conversation

@jaisonerick

Copy link
Copy Markdown
Owner

Summary

Retract v0.1.0 — it was tagged from an off-branch local snapshot (commit 80e247f) that never landed on main. That snapshot predates CI, tests, and the Swift-target pin that shipped in v0.1.1 onward, so consumers who resolved to v0.1.0 would be missing real improvements (including the macOS 13 launch fix from v0.1.3).

Added a retract v0.1.0 directive in go.mod with a reason comment so go list -m -u all surfaces the retraction for anyone on it.

The remote git tag has already been deleted. The Go module proxy cache for v0.1.0 cannot be revoked (proxy caches are permanent by design), so the retract directive is the load-bearing piece.

Test plan

  • go mod tidy preserves the retract
  • After merge + release, go list -m -versions github.com/jaisonerick/macwifi shows v0.1.0 with a (retracted) marker
  • pkg.go.dev renders a "Retracted" notice on the v0.1.0 version page

v0.1.0 was tagged from an off-branch local snapshot that never landed
on main. The code there predates CI, tests, and the Swift-target pin
that shipped in v0.1.1 onward, and consumers who ended up on it would
miss the stapled notarization check and the macOS 13 launch fix.

Adding the retract directive so go tooling warns anyone resolving
v0.1.0 to upgrade to v0.1.1+. The remote git tag has also been
removed; the Go module proxy cache for v0.1.0 is permanent and cannot
be revoked, so the retract is the load-bearing piece.
@jaisonerick
jaisonerick enabled auto-merge (squash) April 22, 2026 01:30
@jaisonerick
jaisonerick merged commit b60b4fb into main Apr 22, 2026
5 checks passed
@jaisonerick
jaisonerick deleted the fix/retract-v0.1.0 branch April 22, 2026 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant