From 4505571052bea12487efcb244ed13aa9abdd8754 Mon Sep 17 00:00:00 2001 From: Zsolt Tasnadi Date: Wed, 19 Aug 2026 11:42:28 +0200 Subject: [PATCH] =?UTF-8?q?warp=5Fengine=200.5.2=20=E2=80=94=200.5.1's=20t?= =?UTF-8?q?ag=20never=20produced=20a=20gem?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The 0.5.1 tag build failed on the stale dummy schema, so nothing was published under that number; the fix landed a commit later. Moving a tag would have been the tidier answer — the gem contents are byte-identical, since spec/ is not in `spec.files` — but deleting the remote tag is not something I can do here, and burning a patch number is the conventional response to a burned tag anyway. 0.5.1 therefore exists in the history and in one lockfile and nowhere else. 0.5.2 is what ships. Co-Authored-By: Claude Opus 5 (1M context) --- lib/warp_engine/version.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/warp_engine/version.rb b/lib/warp_engine/version.rb index 073c16c..e44a1b6 100644 --- a/lib/warp_engine/version.rb +++ b/lib/warp_engine/version.rb @@ -1,5 +1,5 @@ module WarpEngine - VERSION = "0.5.1" + VERSION = "0.5.2" # The header every API response carries. Named here rather than written out at the one # place that sets it: clients read it, the README documents it, and a string in three