create_github_release 0.2.1 → 1.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f086029c9ddf7585de3b2872c59a6d6b4d5449038327cc26703a5dcf31fc5302
-  data.tar.gz: 5c3eba003d79b8c676b8040f1fd359eb1b9a0271c873d70d930cd283eda743bd
+  metadata.gz: b7feefb0f3ef554c8aea3c693cdbbed30aab587be5dc44631101898caadfa658
+  data.tar.gz: d342cd8c38e03ca012d5b70daf832642a7434c647d4466d9cd0969e9f4278926
 SHA512:
-  metadata.gz: 101af2b61d0a4a78b9ad776bf265981152a11134170c67133910e7f7ab3081f169bc5361b490dda4c5a218c2b46e2a22812a30613582d879ffc7080d058225f5
-  data.tar.gz: 6cb1bbdcaa1bc974ef0a684648fb82df1be00ff67de2d50503130ce642bd3f0022935d77a2fdd2af7c4bbd992bde05167e48142d9a3b048ff5b779cd63f57a70
+  metadata.gz: 122c8e2198ceb28fa9e429f851e7c6d821cadc71fb5a3ade6749c520d1ae7d427159f7059e1455a3a2b15294d8e1125e75451d4d1996fceef63f07e7b88b4ffb
+  data.tar.gz: e6d1a7abe65328fc51161458934709b9ae3e747573398f4ef71bcdfad4023f865b76ebd6836fe7622183a90909da9498ca6ec30b29deac89d9608b0a225e8d7d

data/.markdownlint.yml

@@ -1,7 +1,7 @@
 default: true
 
 # Unordered list indentation
-MD007: { indent: 4 }
+MD007: { indent: 2 }
 
 # Line length
 MD013: { line_length: 90, tables: false, code_blocks: false }

data/CHANGELOG.md

@@ -5,6 +5,27 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## v1.0.0 (2023-02-05)
+
+[Full Changelog](https://github.com/main-branch/create_github_release/compare/v0.3.0..v1.0.0)
+
+Changes since v0.3.0:
+
+* bfd40e6 Handle the first release of a gem (#32)
+* 7a76148 Release v0.3.0 (#31)
+
+## v0.3.0 (2023-01-29)
+
+[Full Changelog](https://github.com/main-branch/create_github_release/compare/v0.2.1..v0.3.0)
+
+Changes since v0.2.1:
+
+* 92ce55a Report "no changes" in the release description (#30)
+* 1b3505b Assert that gh has been authenticated (#29)
+* c7bd12d Complete redesign of this gem (#28)
+* d75e1e9 Create release tag after committing release changes (#27)
+* 24bdd02 Release v0.2.1
+
 ## v0.2.1 (2022-11-16)
 
 [Full Changelog](https://github.com/main-branch/create_github_release/compare/v0.2.0...v0.2.1)

data/LICENSE.txt

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2022 James Couball
+Copyright (c) 2023 James Couball
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal

data/README.md

@@ -5,36 +5,27 @@
  [![Maintainability](https://api.codeclimate.com/v1/badges/b8c0af10b15a0ffeb1a1/maintainability)](https://codeclimate.com/github/main-branch/create_github_release/maintainability)
  [![Test Coverage](https://api.codeclimate.com/v1/badges/b8c0af10b15a0ffeb1a1/test_coverage)](https://codeclimate.com/github/main-branch/create_github_release/test_coverage)
 
-Create a GitHub release for a new gem version.
+A script to manage your gem version and create a GitHub branch, PR, and release
+for a new gem version.
 
-To create a new GitHub release for a gem, run the following from the top level
-project directory with the default branch selected:
+Since this script builds a changelog by listing the commits on the default branch,
+it works best if you are disciplined about squashing PR commits to the
+minimum number of commits necessary (usually one) in order to avoid a noisy changelog.
 
-```shell
-create-github-release [major|minor|patch]
-```
+Tested on Ruby 2.7+
 
-The following conditions must be met in order to create a release:
-
-* The bundle must be up to date (via bundle update)
-* You current directory must be in the top level of the git repository
-* The default branch must be checked out
-* There are no uncommitted changes
-* The local and remote must be on the same commit
-* The new release tag must not already exist either locally or remotely
-* The new release branch must not already exist either locally or remotely
-* Docker must be running
-* The changelog docker container must already exist or be able to be built
-* The gh command must be installed
-
-The result of running this command is:
-* A new release branch is created
-* CHANGELOG.md is updated with a list of PRs since the last release
-* The Gem version is updated via Bump
-* The CHANGELOG.md and version changes are committed and tagged on the new release branch
-* The new release branch is pushed to the remote
-* A release is created on GitHub
-* A release PR is created on GitHub
+* [The create\_github\_release Gem](#the-create_github_release-gem)
+  * [Installation](#installation)
+  * [Usage](#usage)
+    * [First release using this script when there were NO prior releases](#first-release-using-this-script-when-there-were-no-prior-releases)
+    * [First release using this script when there were prior releases](#first-release-using-this-script-when-there-were-prior-releases)
+    * [Subsequent releases using this script](#subsequent-releases-using-this-script)
+  * [After Running create-github-release](#after-running-create-github-release)
+  * [How the changelog is updated](#how-the-changelog-is-updated)
+  * [Limitations](#limitations)
+  * [Development](#development)
+  * [Contributing](#contributing)
+  * [License](#license)
 
 ## Installation
 
@@ -46,17 +37,248 @@ spec.add_development_dependency 'create_github_release', '~> 0.1'
 
 and then install using `bundle update`.
 
+## Usage
+
+This gem installs the `create-guthub-release` command line tool:
+
+```text
+Usage:
+create-github-release --help | RELEASE_TYPE [options]
+
+RELEASE_TYPE must be 'major', 'minor', 'patch', or 'first'
+
+Options:
+        --default-branch=BRANCH_NAME Override the default branch
+        --release-branch=BRANCH_NAME Override the release branch to create
+        --remote=REMOTE_NAME         Use this remote name instead of 'origin'
+        --last-release-version=VERSION
+                                     Use this version instead `bump current`
+        --next-release-version=VERSION
+                                     Use this version instead `bump RELEASE_TYPE`
+        --changelog-path=PATH        Use this file instead of CHANGELOG.md
+    -q, --[no-]quiet                 Do not show output
+    -v, --[no-]verbose               Show extra output
+    -h, --help                       Show this message
+```
+
+The RELEASE_TYPE should follow [Semantic Versioning](https://semver.org) rules:
+
+* A **major** release includes incompatible API changes
+* A **minor** release includes added functionality in a backwards compatible manner
+* A **patch** release includes backwards compatible bug fixes or other inconsequential changes
+
+This script will be used for three different use cases:
+
+### First release using this script when there were NO prior releases
+
+If this is to be the first release of this gem follow these instructions.
+
+For this use case, let's assume the following:
+
+* the default branch is `main` (this is the HEAD branch returned by `git remote show origin`)
+* the current version of the gem is `0.1.0` (as returned by `bump current`)
+
+If a different first version number is desired, update the version number in the
+source code making sure that `bump current` returns the desired version number.
+Then commit the change to the default branch on the remote before running this
+script.
+
+You should start with a CHANGELOG.md that just has frontmatter. An empty file or
+no file is also acceptable. It is not recommended to go with the CHANGELOG.md generated
+by `bundle gem`. Here are suggested CHANGELOG.md contents prior to the first release:
+
+```markdown
+# Change Log
+
+Changes for each release are listed in this file.
+
+This project adheres to [Semantic Versioning](https://semver.org/) for its releases.
+```
+
+See [How the changelog is updated](#how-the-changelog-is-updated) for more information.
+
+The following prerequisites are checked by this script:
+
+* The current directory must be in the top level of the git repository
+* The HEAD commit of the default branch (`main`) must be checked out
+* The HEAD commit of the default branch of the local repository must match the
+  HEAD commit of the default branch of the remote repository
+* There are no uncommitted or unstaged changes
+* The bundle must be up to date (the script will attempt to update the bundle if needed)
+* The next-release tag (`v0.1.0`) must NOT already exist
+* The next-release branch (`release-v0.1.0`) must NOT already exist
+* The gh command must be installed and authenticated via `gh auth`
+
+You should run:
+
+```shell
+create-github-release first
+```
+
+The `create-github-release` script will do the following:
+
+* Determine the next-release version (`v0.1.0`) using `bump current`
+* Update the project's changelog file `CHANGELOG.md`
+* Create a release branch `release-v0.1.0`
+* Commit the changes to the changelog and create a release tag (`v0.1.0`) pointing
+  to that commit
+* Push the release branch to GitHub
+* Create a GitHub release and pull request for the release
+
+See [After running create-github-release](#after-running-create-github-release)
+for instructions for completing your release.
+
+### First release using this script when there were prior releases
+
+In order to start using `create-github-release` after you have used some other
+method for managing the gem version and creating releases, you need to ensure the
+following prerequisites are met:
+
+1. that `bump current` is the version of the last release (let's use `1.3.1` as an
+   example).
+2. that there is a corresponding release tag that points to the last commit on the
+   default branch of the previous release. If the last version was `1.3.1`, then
+   the last-release tag should be `v1.3.1`.
+
+Changes to the changelog file to ensure the next-release description is added correctly
+may need to be done. See [How the changelog is updated](#how-the-changelog-is-updated)
+for details.
+
+Any changes needed to make sure these prerequisites are met should merged or pushed
+to the default branch on the remote.
+
+Once these prerequisites are met and any adjustments have been done, follow the
+directions in [Subserquent releases using this script](#subsequent-releases-using-this-script).
+
+See [After running create-github-release](#after-running-create-github-release)
+for instructions for completing your release.
+
+### Subsequent releases using this script
+
+For this use case, let's assume the following:
+
+* you want to create a `major` release
+* the default branch is `main` (this is the HEAD branch returned by `git remote show origin`)
+* the current version of the gem is `0.1.0` (as returned by `bump current`)
+
+The following prerequisites must be met:
+
+* The current directory must be in the top level of the git repository
+* The HEAD commit of the default branch (`main`) must be checked out
+* The HEAD commit of the default branch of the local repository must match the
+  HEAD commit of the default branch of the remote repository
+* There are no uncommitted or unstaged changes
+* The bundle must be up to date (the script will attempt to update the bundle if needed)
+* The last-release tag (`v0.1.0`) must already exist
+* The next-release tag (`v1.0.0`) must NOT already exist
+* The next-release branch (`release-v1.0.0`) must NOT already exist
+* The gh command must be installed and authenticated via `gh auth`
+
+You should run:
+
+```shell
+create-github-release major
+```
+
+The `create-github-release` script will do the following:
+
+* Determine the last-release version using `bump current`
+* Determine the next-release version using `bump show-next RELEASE_TYPE`
+* Bump the project's version using `bump RELEASE_TYPE`
+* Update the project's changelog file `CHANGELOG.md`
+* Create a release branch `release-v1.0.0`
+* Commit the changes to the version and changelog AND create a release tag (`v1.0.0`) pointing
+  to that commit
+* Push the release branch to GitHub
+* Create a GitHub release and pull request for the release
+
+See [After running create-github-release](#after-running-create-github-release)
+for instructions for completing your release.
+
+## After Running create-github-release
+
+If you want to make additional updates to the ChangeLog or make changes as
+part of the release PR, it is best to do them before running this script. If
+you must make changes after running this script, you should do so in additional
+commits on the release branch. Before merging to the default branch, you should
+squash all commits down to ONE commit on the release branch and make sure that
+the new release tag (`v1.0.0` in this example) points to this commit.
+
+If you are happy with the PR, you should approve it in GitHub.
+
+Next, merge the release branch into the default branch **MANUALLY AT THE COMMAND
+LINE** using a fast forward merge with the following commands:
+
+```shell
+git checkout main
+git merge --ff-only release-v1.0.0
+git push
+```
+
+GitHub will automatically close the PR after the `git push` command. These commands
+are output by `create-github-release` so you do not have to memorize them ;)
+
+It is important to use a fast foward marge to ensure that the release tag points
+to the right commit after the merge. GitHub does not allow fast forward merges when
+ merging a PR.
+
+Finally, publish your gem to rubygems.org with the `rake release` command.
+
+## How the changelog is updated
+
+A release description is generated by listing the commits between the last release
+and the next release.
+
+As an example, let's assume the following:
+
+* the last release version was `0.1.0`
+* the next release version will be `1.0.0`
+* there were two changes in the next release:
+  * The first commit has sha `1111111` and a commit message starting with the
+    line 'Add feature 1'
+  * The second commit has sha `2222222` and a commit message starting with the
+    line 'Add feature 2'
+
+The release description will look like this:
+
+```text
+## Release v1.0.0
+
+Full Changelog
+
+Changes since v0.1.0:
+
+* 2222222 Add feature 2
+* 1111111 Add feature 1
+```
+
+The existing changelog file is read and split into two parts: front matter and
+body.
+
+The front matter is everything before the first markdown H2 header. If there is
+no H2 header, the entire file is considered front matter.
+
+The body is everything else in the file (if the file contains an H2 header)
+
+The resulting updated changelog file has the following sections:
+
+1. front matter
+2. next release description
+3. body (including past release descriptions)
+
+## Limitations
+
+* Does not work on Windows
+* Has only been tested on MRI Ruby
+*
+
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run
 `rake spec` to run the tests. You can also run `bin/console` for an interactive
 prompt that will allow you to experiment.
 
-To install this gem onto your local machine, run `bundle exec rake install`. To
-release a new version, update the version number in `version.rb`, and then run
-`bundle exec rake release`, which will create a git tag for the version, push git
-commits and the created tag, and push the `.gem` file to
-[rubygems.org](https://rubygems.org).
+To install this gem onto your local machine, run `bundle exec rake install`.
 
 ## Contributing
 

data/create_github_release.gemspec

@@ -8,8 +8,11 @@ Gem::Specification.new do |spec|
   spec.authors = ['James']
   spec.email = ['jcouball@yahoo.com']
 
-  spec.summary = 'Create a GitHub release PR for a Ruby Gem'
-  spec.description = spec.summary
+  spec.summary = 'A script to create a GitHub release for a Ruby Gem'
+  spec.description = <<~DESCRIPTION
+    A script that manages your gem version and creates a GitHub branch, PR, and
+    release for a new gem version.
+  DESCRIPTION
   spec.homepage = 'https://github.com/main-branch/create_github_release'
   spec.license = 'MIT'
   spec.required_ruby_version = '>= 2.7.0'
@@ -40,6 +43,7 @@ Gem::Specification.new do |spec|
   spec.add_development_dependency 'simplecov', '~> 0.21'
   spec.add_development_dependency 'simplecov-lcov', '~> 0.8'
   spec.add_development_dependency 'solargraph', '~> 0.47'
+  spec.add_development_dependency 'timecop', '~> 0.9'
   spec.add_development_dependency 'yard', '~> 0.9'
   spec.add_development_dependency 'yardstick', '~> 0.9'
 

data/exe/create-github-release

@@ -3,20 +3,24 @@
 
 require 'create_github_release'
 
-options = CreateGithubRelease::CommandLineParser.new.parse(ARGV)
-CreateGithubRelease::ReleaseAssertions.new(options).make_assertions
+options = CreateGithubRelease::CommandLineParser.new.parse(*ARGV)
+pp options if options.verbose
+
+project = CreateGithubRelease::Project.new(options)
+
+CreateGithubRelease::ReleaseAssertions.new(project).make_assertions
 puts unless options.quiet
-CreateGithubRelease::ReleaseTasks.new(options).run
+CreateGithubRelease::ReleaseTasks.new(project).run
 
-puts <<~MESSAGE unless options.quiet
-  Release '#{options.tag}' created successfully
-  See the release notes at #{options.release_url}
+puts <<~MESSAGE unless project.quiet
+  Release '#{project.next_release_tag}' created successfully
+  See the release notes at #{project.release_url}
 
   Next steps:
   * Get someone to review and approve the release pull request
   * Merge the pull request manually from the command line with the following commands:
 
-  git checkout #{options.default_branch}
-  git merge --ff-only #{options.branch}
+  git checkout #{project.default_branch}
+  git merge --ff-only #{project.release_branch}
   git push
 MESSAGE

data/lib/create_github_release/assertion_base.rb

@@ -9,11 +9,14 @@ module CreateGithubRelease
   # @api private
   #
   class AssertionBase
-    # Create a new assertion object and save the given `options`
-    # @param options [CreateGithubRelease::Options] the options
+    # Create a new assertion object and save the given `project`
+    # @param project [CreateGithubRelease::Project] the project to create a release for
     # @api private
-    def initialize(options)
-      @options = options
+    def initialize(project)
+      raise ArgumentError, 'project must be a CreateGithubRelease::Project' unless
+        project.is_a?(CreateGithubRelease::Project)
+
+      @project = project
     end
 
     # This method must be overriden by a subclass
@@ -29,25 +32,25 @@ module CreateGithubRelease
 
     # @!attribute [r] options
     #
-    # The options passed to the assertion object
-    # @return [CreateGithubRelease::Options] the options
+    # The project passed to the assertion object
+    # @return [CreateGithubRelease::Project] the project to create a release for
     # @api private
-    attr_reader :options
+    attr_reader :project
 
-    # Calls `Kernel.print` if the `quiet` flag is not set in the `options`
+    # Calls `Kernel.print` if the `quiet` flag is not set in the `project`
     # @param args [Array] the arguments to pass to `Kernel.print`
     # @return [void]
     # @api private
     def print(*args)
-      super unless options.quiet
+      super unless project.quiet?
     end
 
-    # Calls `Kernel.puts` if the `quiet` flag is not set in the `options`
+    # Calls `Kernel.puts` if the `quiet` flag is not set in the `project`
     # @param args [Array] the arguments to pass to `Kernel.puts`
     # @return [void]
     # @api private
     def puts(*args)
-      super unless options.quiet
+      super unless project.quiet?
     end
 
     # Writes a message to stderr and exits with exitcode 1
@@ -58,5 +61,16 @@ module CreateGithubRelease
       warn "ERROR: #{message}"
       exit 1
     end
+
+    # `true` if the `project.verbose?` flag is `true`
+    # @return [Boolean]
+    # @api private
+    def backtick_debug?
+      project.verbose?
+    end
+
+    # This overrides the backtick operator for this class to output debug
+    # information if `verbose?` is true
+    include CreateGithubRelease::BacktickDebug
   end
 end

data/lib/create_github_release/assertions/bundle_is_up_to_date.rb

@@ -5,7 +5,7 @@ require 'create_github_release/assertion_base'
 
 module CreateGithubRelease
   module Assertions
-    # Assert that options.branch does not exist
+    # Assert that project.release+branch does not exist
     #
     # Checks both the local repository and the remote repository.
     #
@@ -17,8 +17,9 @@ module CreateGithubRelease
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::BundleIsUpToDate.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::BundleIsUpToDate.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'

data/lib/create_github_release/assertions/{docker_is_running.rb → gh_authenticated.rb}

@@ -5,18 +5,19 @@ require 'create_github_release/assertion_base'
 
 module CreateGithubRelease
   module Assertions
-    # Assert that docker is running
+    # Assert that the 'gh' command is in the path
     #
     # @api public
     #
-    class DockerIsRunning < AssertionBase
-      # Make sure that docker is running
+    class GhAuthenticated < AssertionBase
+      # Make sure that the 'gh' command is authenticated
       #
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::DockerIsRunning.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::GhAuthenticated.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'
@@ -29,12 +30,12 @@ module CreateGithubRelease
       # @raise [SystemExit] if the assertion fails
       #
       def assert
-        print 'Checking that docker is installed and running...'
-        `docker info > /dev/null 2>&1`
+        print 'Checking that the gh command is authenticated...'
+        output = `gh auth status 2>&1`
         if $CHILD_STATUS.success?
           puts 'OK'
         else
-          error 'Docker is not installed or not running'
+          error "gh not authenticated:\n#{output}"
         end
       end
     end

data/lib/create_github_release/assertions/gh_command_exists.rb

@@ -15,8 +15,9 @@ module CreateGithubRelease
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::GhCommandExists.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::GhCommandExists.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'

data/lib/create_github_release/assertions/git_command_exists.rb

@@ -15,8 +15,9 @@ module CreateGithubRelease
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::GitCommandExists.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::GitCommandExists.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'

data/lib/create_github_release/assertions/in_git_repo.rb

@@ -17,8 +17,9 @@ module CreateGithubRelease
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::InGitRepo.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::InGitRepo.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'

data/lib/create_github_release/assertions/in_repo_root_directory.rb

@@ -18,8 +18,9 @@ module CreateGithubRelease
       # @example
       #   require 'create_github_release'
       #
-      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
-      #   assertion = CreateGithubRelease::Assertions::InRepoRootDirectory.new(options)
+      #   options = CreateGithubRelease::CommandLineOptions.new { |o| o.release_type = 'major' }
+      #   project = CreateGithubRelease::Project.new(options)
+      #   assertion = CreateGithubRelease::Assertions::InRepoRootDirectory.new(project)
       #   begin
       #     assertion.assert
       #     puts 'Assertion passed'

data/lib/create_github_release/assertions/last_release_tag_exists.rb

@@ -0,0 +1,47 @@
+# frozen_string_literal: true
+
+require 'English'
+require 'create_github_release/assertion_base'
+
+module CreateGithubRelease
+  module Assertions
+    # Assert that the release tag does not exist in the local repository
+    #
+    # @api public
+    #
+    class LastReleaseTagExists < AssertionBase
+      # Assert that the last release tag exists in the local repository
+      #
+      # @example
+      #   require 'create_github_release'
+      #
+      #   options = CreateGithubRelease::Options.new { |o| o.release_type = 'major' }
+      #   assertion = CreateGithubRelease::Assertions::LastReleaseTagExists.new(options)
+      #   begin
+      #     assertion.assert
+      #     puts 'Assertion passed'
+      #   rescue SystemExit
+      #     puts 'Assertion failed'
+      #   end
+      #
+      # @return [void]
+      #
+      # @raise [SystemExit] if the assertion fails
+      #
+      def assert
+        return if project.first_release?
+
+        print "Checking that last release tag '#{project.last_release_tag}' exists..."
+
+        tags = `git tag --list "#{project.last_release_tag}"`.chomp
+        error 'Could not list tags' unless $CHILD_STATUS.success?
+
+        if tags == ''
+          error "Last release tag '#{project.last_release_tag}' does not exist"
+        else
+          puts 'OK'
+        end
+      end
+    end
+  end
+end