deployangel 0.1.30 → 0.1.31
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 +4 -4
- data/CHANGELOG.md +7 -0
- data/lib/deployangel/cli.rb +7 -0
- data/lib/deployangel/version.rb +1 -1
- metadata +1 -1
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: 9645adb2fe301ec8c10cfb61f303d8cdb5465b350889307ff82692814f531d9a
|
|
4
|
+
data.tar.gz: 109ef3ffc37b149229be33b46463564860ceef9168b5eb26b057d82f20d66d71
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: cf9b49285346e69ee69e1fd1ce5cf07bef673cfa0b4cafa9ee06bedf42cf8ba72bb55dfa5d6534247726c5528c447f339436064c7ab23a5bd001506e683f325f
|
|
7
|
+
data.tar.gz: b843e7f6e991b6a7f18a42781be35bef1f353b1580a0d34dce234d39d1ed012393fab3ef227ef8e3bbede6a8b32fb9504883c72783196098ffc2344726642242
|
data/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.31 (2026-10-21)
|
|
4
|
+
|
|
5
|
+
- The instructions `deployangel install agents` writes to `AGENTS.md` now tell
|
|
6
|
+
coding agents to check recent releases and late regressions at the start
|
|
7
|
+
of a session, and to read `fix_check` in the verdict after deploying a fix
|
|
8
|
+
for a failed release. Run it again to update them.
|
|
9
|
+
|
|
3
10
|
## 0.1.30 (2026-10-16)
|
|
4
11
|
|
|
5
12
|
- Hanami 2.2 or later: `require "deployangel/hanami"` and
|
data/lib/deployangel/cli.rb
CHANGED
|
@@ -121,6 +121,13 @@ module DeployAngel
|
|
|
121
121
|
coverage and a full baseline), so don't call a medium clearance weak.
|
|
122
122
|
Warnings (`suspicious: true`) aren't failures: report them as "watching
|
|
123
123
|
closely:" and the `watching_closely` items, never as "suspicious".
|
|
124
|
+
- After deploying a fix for a failed release, read `fix_check` in the verdict
|
|
125
|
+
(`--format=json` with the CLI): `fixed` means every earlier problem is
|
|
126
|
+
healthy again. Otherwise report what's still happening or not confirmed yet.
|
|
127
|
+
- At the start of a session, before changing code: call `list_deployments`
|
|
128
|
+
and `list_late_regressions` (or run `bundle exec deployangel status`). If a
|
|
129
|
+
recent release failed, isn't cleared yet, or has a late regression, mention
|
|
130
|
+
it before other work.
|
|
124
131
|
#{AGENTS_END}
|
|
125
132
|
MARKDOWN
|
|
126
133
|
|
data/lib/deployangel/version.rb
CHANGED