gemsmith 18.7.0 → 18.8.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 41c99ba949d1a07053882c3c7f2e289813fb0c66c8420cf568f29959684c4551
-  data.tar.gz: 4dd69da221db00097951494e0c7a572d6065d4b0ce61940603957d6d5a1f9f37
+  metadata.gz: e30d95770327e819a040434df61830d146c3962cbeee75e3395def23f4840834
+  data.tar.gz: 1fd09fe6424c37674afb171196cbf831ddaefec869d9fa056ece39442d64e0f5
 SHA512:
-  metadata.gz: b0e1d118f6e387a21b0bef43c54d963fbca026a38d4008781c56d73548fb7a24c519c540b9a475073096d096a3d1852ab5e8e784989b9d36bd12bd16b49f2102
-  data.tar.gz: 5d447eb91d48d321e578cae1e23b86b97d0a78faad680c35ed65752231d7471ac5073d2f07c9d6ae745bf3cb8f3f1b6bced2a5fcd761a27ea40707d7b5c3689e
+  metadata.gz: 07a7621edb6757cf3c129ced88000a8e104c5d9c10527d679d5f8b272a0f609c4c63d771786393cb280a96ecc930a25eed68964f0223ccee9b24b1ed6eb30f7f
+  data.tar.gz: 415a9631ed109c71fc02c8e71def5afe9d66ca6d83773fddcb6121eb6286dfc30671932e3ce8717ef18b48832b047d89a497e4523f789010bd44a45cdedc877b

data/README.adoc

@@ -25,15 +25,6 @@ toc::[]
 . link:https://www.ruby-lang.org[Ruby].
 . link:https://rubygems.org[RubyGems].
 
-== Upgrade
-
-If upgrading from 17.0.0 to 18.0.0, you'll want to be aware of the following changes:
-
-* The `--dead_end` build option has been removed.
-* The Milestoner configuration has been updated to support ASCII Doc format by default and the
-  ability to sign tags has been removed (this happens dynamically based on your Git configuration
-  which gives you more flexibility).
-
 == Setup
 
 To install, run:
@@ -93,7 +84,7 @@ BUILD OPTIONS:
       --[no-]cli                           Add command line interface. Default: false.
 ....
 
-=== Build
+==== Build
 
 The core functionality of this gem centers around the `--build` command and associated flags. The
 build options allow you to further customize the kind of gem you want to build. Most build options
@@ -125,7 +116,7 @@ you supports the following options:
 
 From here you can add whatever you wish to make an awesome CLI gem for others to enjoy.
 
-=== Install
+==== Install
 
 After you've designed, implemented, and built your gem, you'll want to test it out within your local
 environment by installing it. You can do this by running:
@@ -143,7 +134,7 @@ Gemsmith can be used to install any gem, in fact. Doesn't matter if the gem was
 Bundler, or some other tool. As long as your gem has a `*.gemspec` file, Gemsmith will be able to
 install it.
 
-=== Publish
+==== Publish
 
 Once you've built your gem; installed it locally; and thoroughly tested it, you'll want to publish
 your gem so anyone in the world can make use of it. You can do this by running the following:
@@ -169,7 +160,7 @@ As with installing a gem, Gemsmith can be used to publish existing gems which we
 Gemsmith too. As long as your gem has a `*.gemspec` file with a valid version, Gemsmith will be able
 to publish it.
 
-=== Edit
+==== Edit
 
 Gemsmith can be used to edit existing gems on your local system. You can do this by running:
 
@@ -184,7 +175,7 @@ have set in your `EDITOR` environment variable).
 
 Editing a local gem is a great way to learn from others or quickly debug issues.
 
-=== View
+==== View
 
 Gemsmith can be used to view existing gem documentation. You can do this by running:
 
@@ -256,9 +247,9 @@ gemsmith --install
 gemsmith --publish
 ----
 
-== Security
+=== Security
 
-=== Git Signing Key
+==== Git Signing Key
 
 To securely sign your Git tags, install and configure link:https://www.gnupg.org[GPG]:
 
@@ -294,7 +285,7 @@ Add your key to your global Git configuration in the `[user]` section. Example:
 Now, when publishing your gems with Gemsmith (i.e. `bundle exec rake publish`), signing of your Git
 tag will happen automatically.
 
-=== Gem Certificates
+==== Gem Certificates
 
 To create a certificate for your gems, run the following:
 
@@ -322,7 +313,7 @@ end
 To learn more about gem certificates, read about RubyGems
 link:https://guides.rubygems.org/security[Security].
 
-== Private Gem Servers
+=== Private Gem Servers
 
 By default, the following command will publicly publish your gem to
 link:https://rubygems.org[RubyGems]:
@@ -336,7 +327,7 @@ You can change this behavior by adding metadata to your gemspec that will allow
 your gem to an alternate/private gem server instead. This can be done by updating your gem
 specification and RubyGems credentials.
 
-=== Gem Specification Metadata
+==== Gem Specification Metadata
 
 Add the following gemspec metadata to privately publish new versions of your gem:
 
@@ -357,7 +348,7 @@ Use of the `allowed_push_host` key provides two important capabilities:
 * Defines the lookup key in your `$HOME/.gem/credentials` file which contains your private
   credentials for authentication to your private server (more on this below).
 
-=== Gem Credentials
+==== Gem Credentials
 
 With your gem specification metadata established, you are ready to publish your gem to a public or
 private server. If this is your first time publishing a gem and no gem credentials have been
@@ -411,7 +402,7 @@ Lastly, should you need to delete a credential (due to a bad login/password for
 open the `$HOME/.gem/credentials` in your default editor and remove the line(s) you don't need. Upon
 next publish of your gem, you'll be prompted for the missing credentials.
 
-=== Bundler Configuration
+==== Bundler Configuration
 
 So far, I've shown how to privately _publish_ a gem but now we need to teach Bundler how to install
 the gem as dependency within your upstream project. For demonstration purposes, I'm going to assume
@@ -454,7 +445,7 @@ Resolving dependencies...Fetching gem metadata from https://rubygems.org/.....
 
 If so, you're all set!
 
-=== GitHub Actions/Packages Automation
+==== GitHub Actions/Packages Automation
 
 Earlier, I hinted at using GitHub Packages but what if you could automate the entire publishing
 process? Well, good news, you can by using GitHub Actions to publish your packages. Here's the YAML
@@ -510,24 +501,13 @@ The above will ensure the following:
 This entire workflow is explained in my
 link:https://www.alchemists.io/talks/ruby_git_hub_packages[talk] on this exact subject too.
 
-== Promotion
-
-Once your gem is released, let the world know about your accomplishment by posting an update to
-these sites:
-
-* link:https://rubyflow.com[RubyFlow]
-* link:https://ruby.libhunt.com[Ruby Library Hunt]
-* link:https://awesome-ruby.com[Awesome Ruby]
-* link:https://www.ruby-toolbox.com[Ruby Toolbox]
-* link:https://www.ruby-lang.org/en/community[Ruby Community]
-
 == Development
 
 To contribute, run:
 
 [source,bash]
 ----
-git clone https://github.com/bkuhlmann/gemsmith.git
+git clone https://github.com/bkuhlmann/gemsmith
 cd gemsmith
 bin/setup
 ----

data/gemsmith.gemspec

@@ -2,7 +2,7 @@
 
 Gem::Specification.new do |spec|
   spec.name = "gemsmith"
-  spec.version = "18.7.0"
+  spec.version = "18.8.0"
   spec.authors = ["Brooke Kuhlmann"]
   spec.email = ["brooke@alchemists.io"]
   spec.homepage = "https://www.alchemists.io/projects/gemsmith"
@@ -24,12 +24,12 @@ Gem::Specification.new do |spec|
 
   spec.required_ruby_version = "~> 3.1"
   spec.add_dependency "cogger", "~> 0.2"
-  spec.add_dependency "dry-container", "~> 0.10"
+  spec.add_dependency "dry-container", "~> 0.11"
   spec.add_dependency "dry-monads", "~> 1.4"
   spec.add_dependency "infusible", "~> 0.0"
   spec.add_dependency "milestoner", "~> 14.2"
   spec.add_dependency "refinements", "~> 9.6"
-  spec.add_dependency "rubysmith", "~> 3.6"
+  spec.add_dependency "rubysmith", "~> 3.7"
   spec.add_dependency "runcom", "~> 8.5"
   spec.add_dependency "spek", "~> 0.5"
   spec.add_dependency "versionaire", "~> 10.5"

data/lib/gemsmith/templates/%project_name%/%project_name%.gemspec.erb

@@ -36,7 +36,7 @@ Gem::Specification.new do |spec|
 
   spec.required_ruby_version = "~> <%= RUBY_VERSION[/\d+\.\d+/] %>"
   <% if configuration.build_cli %>
-    spec.add_dependency "dry-container", "~> 0.10"
+    spec.add_dependency "dry-container", "~> 0.11"
   <% end %>
   <% if configuration.build_cli %>
     spec.add_dependency "infusible", "~> 0.0"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: gemsmith
 version: !ruby/object:Gem::Version
-  version: 18.7.0
+  version: 18.8.0
 platform: ruby
 authors:
 - Brooke Kuhlmann
@@ -28,7 +28,7 @@ cert_chain:
   CxDe2+VuChj4I1nvIHdu+E6XoEVlanUPKmSg6nddhkKn2gC45Kyzh6FZqnzH/CRp
   RFE=
   -----END CERTIFICATE-----
-date: 2022-09-05 00:00:00.000000000 Z
+date: 2022-09-16 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cogger
@@ -50,14 +50,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.10'
+        version: '0.11'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '0.10'
+        version: '0.11'
 - !ruby/object:Gem::Dependency
   name: dry-monads
   requirement: !ruby/object:Gem::Requirement
@@ -120,14 +120,14 @@ dependencies:
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.6'
+        version: '3.7'
   type: :runtime
   prerelease: false
   version_requirements: !ruby/object:Gem::Requirement
     requirements:
     - - "~>"
       - !ruby/object:Gem::Version
-        version: '3.6'
+        version: '3.7'
 - !ruby/object:Gem::Dependency
   name: runcom
   requirement: !ruby/object:Gem::Requirement
@@ -280,7 +280,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.21
+rubygems_version: 3.3.22
 signing_key:
 specification_version: 4
 summary: A command line interface for smithing Ruby gems.