deployangel 0.1.33 → 0.1.34

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eb68d7ed3170cb16932b6ab0de9304c4388e9df001067cf6c0b6678e92fae0d1
-  data.tar.gz: dc867b57741dc75e868284fd8a1f30450d756306fcb891f66331538dacf3486f
+  metadata.gz: 7e0552271dfa638f21feb4c8591729a8c226df32dc75201a12a8e41843534f75
+  data.tar.gz: d62f917c014872a66458dab5e73de67b87b594b0e654b519388d193cd62d4965
 SHA512:
-  metadata.gz: 8427f099ce309a80180e0dbb3033e465e4d82c8ad6f0f72c803623594feb6b9a831a16e7ec25c21e866c792d0acfa50d39f453eb17b2d282f32bd765f8133be4
-  data.tar.gz: 4c19dc7ec0a6730724a466dc51b91f99bddf073b9dc3af480a584ee62417a7637543f64f8f9d4784be176416067162ad79200031e22ed180eb30c70da7ec7072
+  metadata.gz: 9e116aca53991800ed66a98f288fad4706f51baf45b174678156cfcd51202bac16e7d151ef5c323ad97d14f6ca774bf2092f034ef2764fd2106d530f2a48c0ec
+  data.tar.gz: 2f31abc979d9de0d0fac5da35d975025240144df25bc82693c25c5ca271ecb206032437cbfbca61571a78a70559f40b5083e423d98d94f1a35290968fa5b01bd

data/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.34 (2026-11-01)
+
+- `deployangel verify` prints a failed release's next steps: the last
+  cleared release a rollback would go to, with the migrations it would
+  cross, and where to look first. They come from the verdict document's new
+  `next_steps` field, so servers before 2026-11-01 show none. The coding
+  agent instructions mention them, and still say to ask before rolling back.
+
 ## 0.1.33 (2026-10-28)
 
 - An exception whose message has bytes that aren't valid UTF-8, as a

data/README.md

@@ -629,7 +629,8 @@ verdict: call the `wait_for_verification` MCP tool with the commit and
   The release is NOT cleared.
 - Exit 2 / inconclusive: the release is NOT verified. Do not claim success.
 - Exit 1 / failed: read the findings and exceptions (`get_exception`),
-  investigate the likely cause, and propose a fix. Do not roll back or change
+  investigate the likely cause, and propose a fix. `next_steps` names the last
+  cleared release a rollback would go to. Do not roll back or change
   production without explicit approval.
 - Exit 3: still verifying; run the command again.
 - Not cleared yet: call `get_exercise_plan` (or `bundle exec deployangel plan`).

data/lib/deployangel/cli/formatter.rb

@@ -110,7 +110,10 @@ module DeployAngel
           end ],
           [ "Changed but not yet exercised", changed.map { |item| item["key"] } ],
           [ "To clear sooner, exercise (deployangel plan for details)", exercisable_items(document).first(5) ],
-          [ "Late regressions", Array(document["late_regressions"]).map { |late| late["summary"] } ]
+          [ "Late regressions", Array(document["late_regressions"]).map { |late| late["summary"] } ],
+          # A failed release's rollback target and where to look first
+          # (servers from 2026-11-01 send them).
+          [ "Next steps", Array(document["next_steps"]).map { |step| step["text"] } ]
         ].reject { |_, items| items.empty? }
       end
 

data/lib/deployangel/cli.rb

@@ -108,7 +108,8 @@ module DeployAngel
         The release is NOT cleared.
       - Exit 2 / inconclusive: the release is NOT verified. Do not claim success.
       - Exit 1 / failed: read the findings and exceptions (`get_exception`),
-        investigate the likely cause, and propose a fix. Do not roll back or change
+        investigate the likely cause, and propose a fix. `next_steps` names the last
+        cleared release a rollback would go to. Do not roll back or change
         production without explicit approval.
       - Exit 3: still verifying; run the command again.
       - Not cleared yet: call `get_exercise_plan` (or `bundle exec deployangel plan`).

data/lib/deployangel/mcp.rb

@@ -18,7 +18,8 @@ module DeployAngel
         DeployAngel verifies deployments in production. After deploying, call wait_for_verification
         with until "initial" (about 15 minutes) or "verdict". Verdicts: verified means cleared, so you may
         report the release as successful. inconclusive means NOT verified: never report it as success.
-        failed means production regressed: read the findings and exceptions and investigate.
+        failed means production regressed: read the findings and exceptions and investigate. next_steps
+        names the last cleared release a rollback would go to and the migrations it would cross.
         Confidence medium clears a release just as high does (high also needs 80% coverage and a full
         baseline): never call a medium clearance weak. suspicious true means warnings DeployAngel is
         watching closely, not a failure: report them as "watching closely:" and the watching_closely items,

data/lib/deployangel/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module DeployAngel
-  VERSION = "0.1.33"
+  VERSION = "0.1.34"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: deployangel
 version: !ruby/object:Gem::Version
-  version: 0.1.33
+  version: 0.1.34
 platform: ruby
 authors:
 - Jordan Owens