statistrano 1.2.0 → 1.2.1
Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA1:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: b3cf043a12c5f955673727a758f5f8ccfe65e7ed
|
4
|
+
data.tar.gz: e515d09d645bc9db4900446b4d59ec2fc7b86c67
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: a25ad9f76ca4ccd3a859609d640aea135bfb126201d276da1af0ffdbaf258c024cadead3f724e6bc3d61589c2253cf87771ae222eff4fdcc973e52f4ccb0bb68
|
7
|
+
data.tar.gz: 3f0a1b2560058bec04c4952b92f99774eb65d0505eb039c0ed07bf638dc6e96720e4bbbfea1fd68da7f94e894c45d0d3978262b77b3f9a3f93e2e555775ada37
|
data/changelog.md
CHANGED
@@ -1,3 +1,6 @@
|
|
1
|
+
# 1.2.1
|
2
|
+
- fix bug where `Strategy::Branches` wasn't caching manifests, causing the prune task to fail at removing releases from the manifest.
|
3
|
+
|
1
4
|
# 1.2.0
|
2
5
|
- remote specific config is now tied directly to the remote through it's own config object. Internally this cleans up many checks, but causes [BREAKING] changes if you depended on the API of any of the internal classes. If you use config data in any of your tasks, it's now suggested that you do so inside your `remotes` iterators.
|
3
6
|
- get `Strategy::Branches` supporting multiple remotes. The stdout output of `list_releases` and `prune_releases` has changed, so if you depended on this it may be breaking.
|
data/lib/statistrano/version.rb
CHANGED
data/readme.md
CHANGED
@@ -70,6 +70,9 @@ eof
|
|
70
70
|
release_stdin 1 do
|
71
71
|
@deployment.prune_releases
|
72
72
|
expect( Dir[ "deployment/**" ] ).not_to include "deployment/first_branch"
|
73
|
+
|
74
|
+
manifest_json = JSON.parse(IO.read("deployment/manifest.json"))
|
75
|
+
expect( manifest_json.map { |d| d["name"] } ).not_to include "first_branch"
|
73
76
|
end
|
74
77
|
end
|
75
78
|
end
|