warp_engine 0.5.2 — 0.5.1's tag never produced a gem

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) <noreply@anthropic.com>
The dummy schema still stamped the old migration version
2026-08-19 11:42:28 +02:00 · 2026-08-19 11:39:45 +02:00 · 2026-08-19 11:36:43 +02:00
3 changed files with 3 additions and 3 deletions
@@ -1,7 +1,7 @@
 PATH
  remote: ../libs/ruby/warp_engine
  specs:
-    warp_engine (0.5.0)
+    warp_engine (0.5.2)
      apipie-rails
      blueprinter
      rails (>= 8.0)
@@ -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
@@ -10,7 +10,7 @@
 #
 # It's strongly recommended that you check this file into your version control system.

-ActiveRecord::Schema[8.1].define(version: 2026_08_19_000001) do
+ActiveRecord::Schema[8.1].define(version: 2026_08_19_093412) do
  create_table "application_tokens", id: { type: :bigint, unsigned: true }, charset: "utf8mb4", collation: "utf8mb4_0900_ai_ci", force: :cascade do |t|
    t.datetime "created_at", precision: 3
    t.datetime "deleted_at", precision: 3