cartage 2.0 → 2.2.1

Sign up to get free protection for your applications and to get access to all the features.
metadata CHANGED
@@ -1,14 +1,15 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: cartage
3
3
  version: !ruby/object:Gem::Version
4
- version: '2.0'
4
+ version: 2.2.1
5
5
  platform: ruby
6
6
  authors:
7
7
  - Austin Ziegler
8
- autorequire:
8
+ - Kinetic Cafe
9
+ autorequire:
9
10
  bindir: bin
10
11
  cert_chain: []
11
- date: 2016-05-31 00:00:00.000000000 Z
12
+ date: 2022-05-09 00:00:00.000000000 Z
12
13
  dependencies:
13
14
  - !ruby/object:Gem::Dependency
14
15
  name: gli
@@ -30,42 +31,42 @@ dependencies:
30
31
  requirements:
31
32
  - - "~>"
32
33
  - !ruby/object:Gem::Version
33
- version: '5.9'
34
+ version: '5.15'
34
35
  type: :development
35
36
  prerelease: false
36
37
  version_requirements: !ruby/object:Gem::Requirement
37
38
  requirements:
38
39
  - - "~>"
39
40
  - !ruby/object:Gem::Version
40
- version: '5.9'
41
+ version: '5.15'
41
42
  - !ruby/object:Gem::Dependency
42
- name: rdoc
43
+ name: rake
43
44
  requirement: !ruby/object:Gem::Requirement
44
45
  requirements:
45
- - - "~>"
46
+ - - ">="
46
47
  - !ruby/object:Gem::Version
47
- version: '4.0'
48
+ version: '10.0'
48
49
  type: :development
49
50
  prerelease: false
50
51
  version_requirements: !ruby/object:Gem::Requirement
51
52
  requirements:
52
- - - "~>"
53
+ - - ">="
53
54
  - !ruby/object:Gem::Version
54
- version: '4.0'
55
+ version: '10.0'
55
56
  - !ruby/object:Gem::Dependency
56
- name: rake
57
+ name: rdoc
57
58
  requirement: !ruby/object:Gem::Requirement
58
59
  requirements:
59
- - - ">="
60
+ - - "~>"
60
61
  - !ruby/object:Gem::Version
61
- version: '10.0'
62
+ version: '6.4'
62
63
  type: :development
63
64
  prerelease: false
64
65
  version_requirements: !ruby/object:Gem::Requirement
65
66
  requirements:
66
- - - ">="
67
+ - - "~>"
67
68
  - !ruby/object:Gem::Version
68
- version: '10.0'
69
+ version: '6.4'
69
70
  - !ruby/object:Gem::Dependency
70
71
  name: hoe-doofus
71
72
  requirement: !ruby/object:Gem::Requirement
@@ -156,14 +157,14 @@ dependencies:
156
157
  requirements:
157
158
  - - "~>"
158
159
  - !ruby/object:Gem::Version
159
- version: '2.0'
160
+ version: '3.0'
160
161
  type: :development
161
162
  prerelease: false
162
163
  version_requirements: !ruby/object:Gem::Requirement
163
164
  requirements:
164
165
  - - "~>"
165
166
  - !ruby/object:Gem::Version
166
- version: '2.0'
167
+ version: '3.0'
167
168
  - !ruby/object:Gem::Dependency
168
169
  name: minitest-focus
169
170
  requirement: !ruby/object:Gem::Requirement
@@ -226,14 +227,14 @@ dependencies:
226
227
  requirements:
227
228
  - - "~>"
228
229
  - !ruby/object:Gem::Version
229
- version: '3.15'
230
+ version: '3.23'
230
231
  type: :development
231
232
  prerelease: false
232
233
  version_requirements: !ruby/object:Gem::Requirement
233
234
  requirements:
234
235
  - - "~>"
235
236
  - !ruby/object:Gem::Version
236
- version: '3.15'
237
+ version: '3.23'
237
238
  description: |-
238
239
  Cartage provides a repeatable means to create a package for a server-side
239
240
  application that can be used in deployment with a configuration tool like
@@ -241,8 +242,20 @@ description: |-
241
242
  dependencies so that it can be deployed in environments with strict access
242
243
  control rules and without requiring development tool presence on the target
243
244
  server(s).
245
+
246
+ This is the last release of cartage. It's been a fun ride, but Docker-based
247
+ images are our future at Kinetic Commerce. There is one feature that remains
248
+ useful, the release-metadata output. We have created a new, more extensible
249
+ format for which we will be creating a gem to manage this. One example of the
250
+ implementation can be found at:
251
+
252
+ https://github.com/KineticCafe/release-metadata-ts
253
+
254
+ We will also be replacing `cartage-rack` with a new gem supporting this new
255
+ format.
244
256
  email:
245
257
  - aziegler@kineticcafe.com
258
+ - dev@kineticcafe.com
246
259
  executables:
247
260
  - cartage
248
261
  extensions: []
@@ -273,6 +286,7 @@ files:
273
286
  - lib/cartage/commands/echo.rb
274
287
  - lib/cartage/commands/info.rb
275
288
  - lib/cartage/commands/manifest.rb
289
+ - lib/cartage/commands/metadata.rb
276
290
  - lib/cartage/commands/pack.rb
277
291
  - lib/cartage/config.rb
278
292
  - lib/cartage/core.rb
@@ -291,8 +305,21 @@ files:
291
305
  homepage: https://github.com/KineticCafe/cartage/
292
306
  licenses:
293
307
  - MIT
294
- metadata: {}
295
- post_install_message:
308
+ metadata:
309
+ source_code_uri: https://github.com/KineticCafe/cartage/
310
+ documentation_uri: http://www.rubydoc.info/github/KineticCafe/cartage/master
311
+ rubygems_mfa_required: 'true'
312
+ post_install_message: |
313
+ This is the last release of cartage. It's been a fun ride, but Docker-
314
+ based images are our future at Kinetic Commerce. There is one feature
315
+ that remains useful, the release-metadata output. We have created a
316
+ new, more extensible format for which we will be creating a gem to
317
+ manage this. One example of the implementation can be found at:
318
+
319
+ https://github.com/KineticCafe/release-metadata-ts
320
+
321
+ We will also be replacing `cartage-rack` with a new gem supporting
322
+ this new format.
296
323
  rdoc_options:
297
324
  - "--main"
298
325
  - README.rdoc
@@ -300,18 +327,17 @@ require_paths:
300
327
  - lib
301
328
  required_ruby_version: !ruby/object:Gem::Requirement
302
329
  requirements:
303
- - - "~>"
330
+ - - ">="
304
331
  - !ruby/object:Gem::Version
305
- version: '2.0'
332
+ version: '0'
306
333
  required_rubygems_version: !ruby/object:Gem::Requirement
307
334
  requirements:
308
335
  - - ">="
309
336
  - !ruby/object:Gem::Version
310
337
  version: '0'
311
338
  requirements: []
312
- rubyforge_project:
313
- rubygems_version: 2.6.4
314
- signing_key:
339
+ rubygems_version: 3.3.13
340
+ signing_key:
315
341
  specification_version: 4
316
342
  summary: Cartage provides a repeatable means to create a package for a server-side
317
343
  application that can be used in deployment with a configuration tool like Ansible,