deployangel 0.1.42 → 0.1.43

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 33fd1151c7e090754dcfa51ced575d52281964abe14f285b46744c2d7c7f8b5c
4
- data.tar.gz: 1e54552a26d6935c70c8abc92860128af5eaacb7545fc6f555d47508e2f81d7f
3
+ metadata.gz: ce8544c5aa3368fc5df3c437726bcb157edec54cfa43b90814c3ae0b4e5777dc
4
+ data.tar.gz: c2cd5fec697b3fc987043ab6aaaf361d34050cd4979ee397dfcf452b3b94dcf4
5
5
  SHA512:
6
- metadata.gz: 0465d87b3ebd9e3a67c7260fe71179c9d44baa01ec7772a77cfa8802f32a99991cf0267d98a65701f1b98fb0e6067b691bb7c5644bcdf148680d1d4d7ae69ddc
7
- data.tar.gz: 3c3231b3af88dc4831479309d8631a29b721d8c9527ce0cb6247974db7d6c4e35ded6e3b9cd0ca38228ce08b8c528f04f91349e2fb43b7cc581daab7403c8d63
6
+ metadata.gz: 0ca495f1e92256a66a96e5b020baaeb75680904be1a89407ba9250e1396f64c3d9441b02b6b59968e3c453c827c4cf76f5850ae405a084ed3567c6ce776e9d82
7
+ data.tar.gz: 0e6ff274dbf1cf28bea67fbc6ab46f13009ebeef1b3d9a7967ceaa874363ec195f99ee3e2144423107594f10a256fd6483c916d3ed65155a1e0fee8427928683
data/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Changelog
2
2
 
3
+ ## 0.1.43 (2026-11-05)
4
+
5
+ - The MCP server's instructions, and the block `deployangel install agents`
6
+ writes, say a failing `p95_latency` finding with an `accept_url` may be an
7
+ intended slowdown, such as a page that now does more work: as with a volume
8
+ or checkpoint drop, a coding agent hands the link to a person with its
9
+ evidence, never accepts it (servers from 2026-11-05).
10
+
3
11
  ## 0.1.42 (2026-11-05)
4
12
 
5
13
  - `deployangel verify` marks a late regression that someone dismissed as a
@@ -112,10 +112,11 @@ module DeployAngel
112
112
  investigate the likely cause, and propose a fix. `next_steps` names the last
113
113
  cleared release a rollback would go to. Do not roll back or change
114
114
  production without explicit approval.
115
- - A failed release whose failing finding is a volume or checkpoint drop you
116
- made on purpose (a route or job you removed): you can't accept it. Tell the
117
- user why you think it was intended, with your evidence, and give them the
118
- finding's `accept_url` so a person decides. It stays failed until then.
115
+ - A failed release whose failing finding is a volume or checkpoint drop or a
116
+ slowdown you made on purpose (a route or job you removed, a page that now
117
+ does more work): you can't accept it. Tell the user why you think it was
118
+ intended, with your evidence, and give them the finding's `accept_url` so a
119
+ person decides. It stays failed until then.
119
120
  - Exit 3: still verifying; run the command again.
120
121
  - Not cleared yet: call `get_exercise_plan` (or `bundle exec deployangel plan`).
121
122
  If its status is "exercisable" or "waiting_for_activity", run
@@ -31,10 +31,11 @@ module DeployAngel
31
31
  Only act on status "exercisable" or "waiting_for_activity"; for "warm_up" or
32
32
  "no_baseline" nothing you run can clear it. Exercise routes marked mutating only with a test account
33
33
  or after asking. Report what you ran with the plan's report_with command (deployangel check).
34
- A failing volume_drop or checkpoint_rate finding with an accept_url may be an intended change, such as
35
- a route or job you removed on purpose. You cannot accept it, and must not try: tell the user why you
36
- think it was intended, with your evidence, and give them the accept_url so a person decides. Until
37
- someone accepts it, the release is failed: never report it as success. A finding with status
34
+ A failing volume_drop, checkpoint_rate, or p95_latency finding with an accept_url may be an intended
35
+ change, such as a route or job you removed on purpose, or a page that now does more work.
36
+ You cannot accept it, and must not try: tell the user why you think it was intended, with your
37
+ evidence, and give them the accept_url so a person decides. Until someone accepts it, the release
38
+ is failed: never report it as success. A finding with status
38
39
  accepted was accepted as intended by the person in accepted_as_intended.
39
40
  TEXT
40
41
 
@@ -1,5 +1,5 @@
1
1
  # frozen_string_literal: true
2
2
 
3
3
  module DeployAngel
4
- VERSION = "0.1.42"
4
+ VERSION = "0.1.43"
5
5
  end
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: deployangel
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.1.42
4
+ version: 0.1.43
5
5
  platform: ruby
6
6
  authors:
7
7
  - Jordan Owens