git-maintain 0.2.0.pre.1.g7946fbc → 0.2.0.pre.2.g229b454

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.
Files changed (4) hide show
  1. checksums.yaml +4 -4
  2. data/CHANGELOG +6 -1
  3. data/README.md +1 -1
  4. metadata +16 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: dba9e32804160431357411f815ac7cbc9c99dbbfc2f7e6d10111c0e7d78a963a
4
- data.tar.gz: b8438a7dc38170a85b14d4e037b0356b2bab6aa113878ed20461280195a357d2
3
+ metadata.gz: a427a9cf371c53e66cd009d6e590678ae440e2daf81144bc9ef618acc0191677
4
+ data.tar.gz: bb9d9b005b0b302d41cf09d9513ae51f391f98b8d7bc25e9b60edf0aa6dcb3c4
5
5
  SHA512:
6
- metadata.gz: fe211f2296c2499994fba6558c5dc6d8f6f401f0f21aa958c1787b6a7d58c6db038c13b8457b06e33cf02c9d057276f40ad50198158ff8d72b176612f1bc6a7b
7
- data.tar.gz: 2594e941d1f40311eaf1726944ef80ff745ccfa04b73d8a1123a79637cde6a92568d377e1bd5e51603deccf065cd2b25a5155d7b101b91485857cd5fe0fbc8cc
6
+ metadata.gz: 1cad5a8b34790b1d4cb1a85031a8347116172d94005379f766b67b4bcb251a586cd86af22e2996c66e329148098060b1e3cc63010011ba1d615f869ed4efa644
7
+ data.tar.gz: 2d7ad65bb96ba9242c2ab550f9a04ed488db31383195a5cfa76e01e4c74280452ebf61b115f5cbe50175b43a8b524d2cc9cc3a6ddb960298c181239463b80f71
data/CHANGELOG CHANGED
@@ -1,4 +1,9 @@
1
- 0.2.0 (2018-07-213)
1
+ 0.2.1 (2018-07-13)
2
+ ------------------
3
+ * Add dependency to github-release
4
+
5
+ * Initial release.
6
+ 0.2.0 (2018-07-13)
2
7
  ------------------
3
8
 
4
9
  * Initial release.
data/README.md CHANGED
@@ -4,7 +4,7 @@ The idea is to script most of the maintenance tasks so the maintainer can focus
4
4
 
5
5
  - Note: the workflow is highly inspired to the git-topic-branches (https://github.com/nmorey/git-topic-branches)
6
6
  and both can be used at the same time
7
- - Note2: Releasing on github is done through the git-release (https://github.com/mpalmer/github-release)
7
+ - Note2: Releasing on github is done through github-release gem (https://github.com/mpalmer/github-release)
8
8
 
9
9
  # Command summary
10
10
 
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: git-maintain
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.2.0.pre.1.g7946fbc
4
+ version: 0.2.0.pre.2.g229b454
5
5
  platform: ruby
6
6
  authors:
7
7
  - Nicolas Morey-Chaisemartin
@@ -9,7 +9,21 @@ autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
11
  date: 2018-07-13 00:00:00.000000000 Z
12
- dependencies: []
12
+ dependencies:
13
+ - !ruby/object:Gem::Dependency
14
+ name: github-release
15
+ requirement: !ruby/object:Gem::Requirement
16
+ requirements:
17
+ - - ">="
18
+ - !ruby/object:Gem::Version
19
+ version: '0'
20
+ type: :runtime
21
+ prerelease: false
22
+ version_requirements: !ruby/object:Gem::Requirement
23
+ requirements:
24
+ - - ">="
25
+ - !ruby/object:Gem::Version
26
+ version: '0'
13
27
  description: |-
14
28
  Be lazy and let git-maintain do all the heavy lifting for maintaining stable branches.
15
29
  Leaves you only with the essential: reviewing the selected patches and decide where they should go.