@@ -66,9 +66,9 @@ Options:
6666 -t, --pre-type=TYPE Type of pre-release to create (e.g. alpha, beta, etc.)
6767 --remote=REMOTE_NAME Use this remote name instead of 'origin'
6868 --last-release-version=VERSION
69- Use this version instead `semverify current`
69+ Use this version instead `gem-version-boss current`
7070 --next-release-version=VERSION
71- Use this version instead `semverify next-RELEASE_TYPE`
71+ Use this version instead `gem-version-boss next-RELEASE_TYPE`
7272 --changelog-path=PATH Use this file instead of CHANGELOG.md
7373 -q, --[no-]quiet Do not show output
7474 -v, --[no-]verbose Show extra output
@@ -90,10 +90,10 @@ If this is to be the first release of this gem follow these instructions.
9090For this use case, let's assume the following:
9191
9292* the default branch is ` main ` (this is the HEAD branch returned by ` git remote show origin ` )
93- * the current version of the gem is ` 0.1.0 ` (as returned by ` semverify current` )
93+ * the current version of the gem is ` 0.1.0 ` (as returned by ` gem-version-boss current` )
9494
9595If a different first version number is desired, update the version number in the
96- source code making sure that ` semverify current` returns the desired version number.
96+ source code making sure that ` gem-version-boss current` returns the desired version number.
9797Then commit the change to the default branch on the remote before running this
9898script.
9999
@@ -131,7 +131,7 @@ create-github-release first
131131
132132The ` create-github-release ` script will do the following:
133133
134- * Determine the next-release version (` v0.1.0 ` ) using ` semverify current`
134+ * Determine the next-release version (` v0.1.0 ` ) using ` gem-version-boss current`
135135* Update the project's changelog file ` CHANGELOG.md `
136136* Create a release branch ` release-v0.1.0 `
137137* Commit the changes to the changelog and create a release tag (` v0.1.0 ` ) pointing
@@ -148,7 +148,7 @@ In order to start using `create-github-release` after you have used some other
148148method for managing the gem version and creating releases, you need to ensure the
149149following prerequisites are met:
150150
151- 1 . that ` semverify current` is the version of the last release (let's use ` 1.3.1 ` as an
151+ 1 . that ` gem-version-boss current` is the version of the last release (let's use ` 1.3.1 ` as an
152152 example).
1531532 . that there is a corresponding release tag that points to the last commit on the
154154 default branch of the previous release. If the last version was ` 1.3.1 ` , then
@@ -173,7 +173,7 @@ For this use case, let's assume the following:
173173
174174* you want to create a ` major ` release
175175* the default branch is ` main ` (this is the HEAD branch returned by ` git remote show origin ` )
176- * the current version of the gem is ` 0.1.0 ` (as returned by ` semverify current` )
176+ * the current version of the gem is ` 0.1.0 ` (as returned by ` gem-version-boss current` )
177177
178178The following prerequisites must be met:
179179
@@ -196,9 +196,9 @@ create-github-release major
196196
197197The ` create-github-release ` script will do the following:
198198
199- * Determine the last-release version using ` semverify current`
200- * Determine the next-release version using ` semverify RELEASE_TYPE --dry-run`
201- * Increment the project's version using ` semverify RELEASE_TYPE`
199+ * Determine the last-release version using ` gem-version-boss current`
200+ * Determine the next-release version using ` gem-version-boss RELEASE_TYPE --dry-run`
201+ * Increment the project's version using ` gem-version-boss RELEASE_TYPE`
202202* Update the project's changelog file ` CHANGELOG.md `
203203* Create a release branch ` release-v1.0.0 `
204204* Commit the changes to the version and changelog AND create a release tag (` v1.0.0 ` ) pointing
0 commit comments