From 53867ac3f1076c2d5c2790f59034c8e2e12b00ae Mon Sep 17 00:00:00 2001
From: Arran Schlosberg <519948+ARR4N@users.noreply.github.com>
Date: Fri, 14 Feb 2025 18:09:50 +0000
Subject: [PATCH] chore: retract `v1.13.14-0.1.0.rc-2` (#141)

## Why this should be merged

Our initial release tags weren't well-formed for our needs. Although the
format was locked in in #81, I still stuffed up rc2. With the upcoming
rc3 release, we want to ensure that Go tooling picks it up as the
latest, which requires retracting rc2 as its format means it will take
higher precedence.

## How this works

`go.mod` `retract`

## How this was tested

n/a
---
 go.mod | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/go.mod b/go.mod
index 90a7c0460c..319aa4f78b 100644
--- a/go.mod
+++ b/go.mod
@@ -2,7 +2,11 @@ module github.com/ava-labs/libevm
 
 go 1.20
 
-retract v1.13.14-0.1.0-rc.1 // bad semver format ("0-rc" grouping) considered > .rc-2
+retract (
+	// Bad semver formats resulting in incorrect precedence
+	v1.13.14-0.1.0-rc.1
+	v1.13.14-0.1.0.rc-2
+)
 
 require (
 	github.com/Azure/azure-sdk-for-go/sdk/storage/azblob v1.2.0