version_boss 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA256:
+  metadata.gz: afacba1102b1a2c3121168da6d563fe07fa20bf819d816dc6c5a6ad5ed6a9e76
+  data.tar.gz: 2dec6257f24013a38fcc27d13cc9e9b41d5149c5f4dbf0a5df095a38dfb3682b
+SHA512:
+  metadata.gz: ecca5ca9fa2f05359ce747ec54fbba9d1b6e89fa9803593628e9fbf26fa2d61ee7a06bfaefc56dd3995c2df6966eb2417111a00e555910f55e78d4c420c4eefc
+  data.tar.gz: 0ad28ede7cb492243f39413d4b9e373315604d37ecbaeb221f5f3df308670c24355450dcb74f26c500bad354b32919cbb0dfd87dec1cf717eb91ef285fa55fb9

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,36 @@
+AllCops:
+  NewCops: enable
+  # Output extra information for each offense to make it easier to diagnose:
+  DisplayCopNames: true
+  DisplayStyleGuide: true
+  ExtraDetails: true
+  SuggestExtensions: false
+  # RuboCop enforces rules depending on the oldest version of Ruby which
+  # your project supports:
+  TargetRubyVersion: 3.0
+
+Gemspec/DevelopmentDependencies:
+  EnforcedStyle: gemspec
+
+# The default max line length is 80 characters
+Layout/LineLength:
+  Max: 120
+
+# The DSL for RSpec and the gemspec file make it very hard to limit block length:
+Metrics/BlockLength:
+  Exclude:
+    - "spec/spec_helper.rb"
+    - "spec/**/*_spec.rb"
+    - "*.gemspec"
+
+Metrics/ModuleLength:
+  CountAsOne: ['hash']
+
+# When writing minitest tests, it is very hard to limit test class length:
+Metrics/ClassLength:
+  CountAsOne: ['hash']
+  Exclude:
+    - "test/**/*_test.rb"
+
+Style/AsciiComments:
+  Enabled: false

data/.yardopts

@@ -0,0 +1,6 @@
+--no-private
+--hide-void-return
+--markup-provider=redcarpet
+--markup markdown
+- CHANGELOG.md
+- LICENSE.txt

data/CHANGELOG.md

@@ -0,0 +1,119 @@
+## v0.1.0 (2024-05-07)
+
+[Full Changelog](https://github.com/main-branch/version_boss/compare/26b5491..v0.1.0)
+
+Changes:
+
+* f802a44 Set initial version number
+* f43d795 Create prerelease without dot like "1.0.0.pre1" instead of "1.0.0.pre.1"
+* 7ba673a Rename the script 'gem-version' to 'gem-version-boss'
+* 16dfc48 Fix YARD in Rakefile and coverage
+* 53a6e1b Remove build_metadata from Gem versions (#36)
+* 0ecd483 Update Code Climate ID after renaming the repository (#35)
+* f83acac Update Code Climate ID after renaming the repository (#34)
+* b8b78dc Rename the gem from semverify to version_boss (#32)
+* 3d14540 Update README.md for the Semverify::Gem class (#31)
+* 562bac9 Remove the "sig" directory from Git (#30)
+* 5d0c857 Separate gem code and semver code into their own modules (#29)
+* 4c85840 Add Gem version functionality (#27)
+* 7404b15 Release v0.3.4
+* cf1dd7c Add env coverage options to use when running rspec (#25)
+* 4e5cc25 Add command line examples to the README.md (#24)
+* 46323a8 Release v0.3.3
+* 8219bf1 Remove markdown from gemspec description (#21)
+* 7c1585b Release v0.3.2
+* 91c3780 Update README and gemspec introduction text (#19)
+* 0d584a8 Release v0.3.1
+* 51f649f Add Ruby 3.3 to CI build (#17)
+* 3255436 Update rubocop configuration for new Rubocop changes (#15)
+* 4cbeb23 Release v0.3.0
+* 83cf403 Update CodeClimate badges after project rename (#13)
+* 7079244 Rename gem from 'semversion' to 'semverify' (#11)
+* 64ae102 Release v0.2.0
+* 7a8069c Integrate the create_github_release gem (#9)
+* 96cdae4 Add Library Usage documentation to README.md (#8)
+* 8196c2e Add JRuby Linux and Windows builds to CI builds (#7)
+* e6b0739 Add windows build to CI builds (#6)
+* 59e310f Fix reported CodeClimate complexity issues (#3)
+* 2d28b30 Integrate CodeClimate maintainability and test coverage tracking (#1)
+* 2bda849 Add CODEOWNERS file to indicate who can review PRs
+* 4599554 Add the CommandLine class and semversion script
+* 6204835 Add the #next_release method to IncrementableSemver
+* 4219c88 Add the #next_pre method to IncrementableSemver
+* 6f3bd22 Add the #next_major, #next_minor, #next_patch methods to IncrementableSemver
+* 76782ac Add the IncrementableSemver class
+* 98d12cc Add the VersionFile and the VersionFileFactory classes
+* 713fddd Add the Semver class
+* e5c9864 Update README.md
+* 26b5491 Initial version
+
+## v0.3.4 (2024-01-20)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.3.3..v0.3.4)
+
+Changes since v0.3.3:
+
+* cf1dd7c Add env coverage options to use when running rspec (#25)
+* 4e5cc25 Add command line examples to the README.md (#24)
+
+## v0.3.3 (2024-01-11)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.3.2..v0.3.3)
+
+Changes since v0.3.2:
+
+* 8219bf1 Remove markdown from gemspec description (#21)
+
+## v0.3.2 (2024-01-11)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.3.1..v0.3.2)
+
+Changes since v0.3.1:
+
+* 91c3780 Update README and gemspec introduction text (#19)
+
+## v0.3.1 (2024-01-05)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.3.0..v0.3.1)
+
+Changes since v0.3.0:
+
+* 51f649f Add Ruby 3.3 to CI build (#17)
+* 3255436 Update rubocop configuration for new Rubocop changes (#15)
+
+## v0.3.0 (2023-03-19)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.2.0..v0.3.0)
+
+Changes since v0.2.0:
+
+* 83cf403 Update CodeClimate badges after project rename (#13)
+* 7079244 Rename gem from 'semversion' to 'semverify' (#11)
+
+## v0.2.0 (2023-03-18)
+
+[Full Changelog](https://github.com/main-branch/semverify/compare/v0.1.0..v0.2.0)
+
+Changes since v0.1.0:
+
+* 7a8069c Integrate the create_github_release gem (#9)
+* 96cdae4 Add Library Usage documentation to README.md (#8)
+* 8196c2e Add JRuby Linux and Windows builds to CI builds (#7)
+* e6b0739 Add windows build to CI builds (#6)
+* 59e310f Fix reported CodeClimate complexity issues (#3)
+* 2d28b30 Integrate CodeClimate maintainability and test coverage tracking (#1)
+* 2bda849 Add CODEOWNERS file to indicate who can review PRs
+* 4599554 Add the CommandLine class and semverify script
+* 6204835 Add the #next_release method to IncrementableSemver
+* 4219c88 Add the #next_pre method to IncrementableSemver
+* 6f3bd22 Add the #next_major, #next_minor, #next_patch methods to IncrementableSemver
+* 76782ac Add the IncrementableSemver class
+* 98d12cc Add the VersionFile and the VersionFileFactory classes
+* 713fddd Add the Semver class
+* e5c9864 Update README.md
+
+## [Unreleased]
+
+## [0.1.0] - 2023-03-10
+
+- Initial release

data/CODE_OF_CONDUCT.md

@@ -0,0 +1,84 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at jcouball@yahoo.com. All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior,  harassment of an individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.0,
+available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.

data/Gemfile

@@ -0,0 +1,6 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+
+# Specify your gem's dependencies in version_boss.gemspec
+gemspec

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+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
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -0,0 +1,199 @@
+# Version Boss
+
+[![Gem Version](https://badge.fury.io/rb/version_boss.svg)](https://badge.fury.io/rb/version_boss)
+[![Documentation](https://img.shields.io/badge/Documentation-Latest-green)](https://rubydoc.info/gems/version_boss/)
+[![Change Log](https://img.shields.io/badge/CHANGELOG-Latest-green)](https://rubydoc.info/gems/version_boss/file/CHANGELOG.md)
+[![Build Status](https://github.com/main-branch/version_boss/workflows/CI%20Build/badge.svg?branch=main)](https://github.com/main-branch/version_boss/actions?query=workflow%3ACI%20Build)
+[![Maintainability](https://api.codeclimate.com/v1/badges/44a42ed085fe162e5dff/maintainability)](https://codeclimate.com/github/main-branch/version_boss/maintainability)
+[![Test Coverage](https://api.codeclimate.com/v1/badges/44a42ed085fe162e5dff/test_coverage)](https://codeclimate.com/github/main-branch/version_boss/test_coverage)
+
+Parse, compare, and increment Gem and Semver versions.
+
+This gem installs the `gem-version-boss` CLI tool to display and increment a gem's version
+based on SemVer rules.
+
+`gem-version-boss` can replace the `bump` command from the [bump
+gem](https://rubygems.org/gems/bump/) for incrementing gem version strings.
+
+How `gem-version-boss` differs from `bump`:
+
+* `gem-version-boss` can manage pre-release versions
+* `bump` can commit and tag the version file changes it makes. There is no plan to
+  add this functionality to `gem-version-boss`.
+* `bump` can update the version in extra files you to specify extra files to
+  increment the version in
+
+Example CLI commands:
+
+```shell
+# Increment the gem version
+gem-version-boss {next-major|next-minor|next-patch} [--pre [--pretype=TYPE]] [--dryrun]
+gem-version-boss next-pre [--pretype=TYPE] [--dryrun]
+gem-version-boss next-release [--dryrun]
+
+# Command to display the current gem version
+gem-version-boss current
+
+# Display the gem version file
+gem-version-boss file
+
+# Validate that a version conforms to SemVer 2.0.0
+gem-version-boss validate VERSION
+
+# Get more detailed help for each command listed above
+gem-version-boss help [COMMAND]
+```
+
+* [Installation](#installation)
+* [Command Line](#command-line)
+  * [Usage](#usage)
+  * [Examples](#examples)
+* [Library Usage](#library-usage)
+  * [VersionBoss::Gem classes](#versionbossgem-classes)
+  * [VersionBoss::Semver classes](#versionbosssemver-classes)
+* [Development](#development)
+* [Contributing](#contributing)
+* [License](#license)
+
+## Installation
+
+Install the gem and add to the application's Gemfile by executing:
+
+```shell
+bundle add version_boss
+```
+
+If bundler is not being used to manage dependencies, install the gem by executing:
+
+```shell
+gem install version_boss --group=development
+```
+
+## Command Line
+
+### Usage
+
+The `gem-version-boss` command line has built in help for all its commands. List the
+commands by invoking `gem-version-boss` with no arguments or `gem-version-boss help` as
+follows:
+
+```shell
+gem-version-boss help
+```
+
+The output is the following:
+
+```shell
+Commands:
+  gem-version-boss current [-q]                                   # Show the current gem version
+  gem-version-boss file [-q]                                      # Show the path to the file containing the gem version
+  gem-version-boss help [COMMAND]                                 # Describe available commands or one specific command
+  gem-version-boss next-major [VERSION] [-p [-t TYPE]] [-n] [-q]  # Increment the version's major part
+  gem-version-boss next-minor [VERSION] [-p [-t TYPE]] [-n] [-q]  # Increment the version's minor part
+  gem-version-boss next-patch [VERSION] [-p [-t TYPE]] [-n] [-q]  # Increment the version's patch part
+  gem-version-boss next-pre [VERSION] [-t TYPE] [-n] [-q]         # Increment the version's pre-release part
+  gem-version-boss next-release [VERSION] [-n] [-q]               # Increment a pre-release version to the release version
+  gem-version-boss validate VERSION [-q]                          # Validate the given version
+```
+
+The `gem-version-boss help COMMAND` command will give further help for a specific command:
+
+```shell
+gem-version-boss help current
+```
+
+The output is the following:
+
+```shell
+Usage:
+  gem-version-boss current [-q]
+
+Options:
+  -q, [--quiet], [--no-quiet], [--skip-quiet]  # Do not print the current version to stdout
+
+Description:
+  Output the current gem version from the file that stores the gem version.
+
+  The command fails if the gem version could not be found or is invalid.
+
+  Use `--quiet` to ensure that a gem version could be found and is valid without producing any output.
+```
+
+### Examples
+
+```shell
+gem-version-boss current # 0.1.0
+
+gem-version-boss validate 1.0.0 # exitcode=0
+gem-version-boss validate bad_version # exitcode=1
+
+gem-version-boss next-patch # 0.1.0 -> 0.1.1
+gem-version-boss next-minor # 0.1.1 -> 0.2.0
+gem-version-boss next-major # 0.2.0 -> 1.0.0
+
+# Pre-release with default pre-release type
+gem-version-boss next-major --pre # 0.1.1 -> 1.0.0.pre1
+
+# Pre-release with non-default pre-release type
+gem-version-boss next-major --pre --pre-type=alpha # 0.1.1 -> 2.0.0-alpha1
+
+# Increment pre-release
+gem-version-boss next-pre # 1.0.0-alpha1 -> 1.0.0-alpha2
+
+# Change the pre-release type
+gem-version-boss pre --pre-type=beta # 1.0.0-alpha2 -> 1.0.0-beta1
+
+# Create release from pre-release
+gem-version-boss release # 1.0.0-beta1 -> 1.0.0
+```
+
+This gem also provides the following classes:
+
+## Library Usage
+
+[Detailed API documenation](https://rubydoc.info/gems/version_boss/) is hosted on
+rubygems.org.
+
+The main classes are:
+
+### VersionBoss::Gem classes
+
+* **VersionBoss::Gem::Version** knows how to parse, validate, and compare [Ruby Gem
+  version strings](https://guides.rubygems.org/patterns/#semantic-versioning).
+
+* **VersionBoss::Gem::IncrementableVersion** knows how to increment Ruby Gem version
+  strings according to SemVer rules.
+
+* **VersionBoss::Gem::VersionFileFactory**: find the gem's version file and returns a
+  **VersionBoss::Gem::VersionFile** that knows it's path, the contained version, and
+  how to update the version file with a new version.
+
+### VersionBoss::Semver classes
+
+* **VersionBoss::Semver::Version** knows how to parse, validate, and compare version
+  strings that conform to [SemVer 2.0.0](https://semver.org/spec/v2.0.0.html)
+
+* **VersionBoss::Semver::IncrementableVersion** knows how to increment Semver version
+  strings according to SemVer rules.
+
+## 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).
+
+## Contributing
+
+Bug reports and pull requests are welcome on GitHub at
+https://github.com/main-branch/version_boss.
+
+## License
+
+The gem is available as open source under the terms of the [MIT
+License](https://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,92 @@
+# frozen_string_literal: true
+
+desc 'Run the same tasks that the CI build will run'
+if RUBY_PLATFORM == 'java'
+  task default: %w[spec rubocop bundle:audit build]
+else
+  task default: %w[spec rubocop yard bundle:audit build]
+end
+
+# Bundler Audit
+
+require 'bundler/audit/task'
+Bundler::Audit::Task.new
+
+# Bundler Gem Build
+
+require 'bundler'
+require 'bundler/gem_tasks'
+
+begin
+  Bundler.setup(:default, :development)
+rescue Bundler::BundlerError => e
+  warn e.message
+  warn 'Run `bundle install` to install missing gems'
+  exit e.status_code
+end
+
+CLEAN << 'pkg'
+CLEAN << 'Gemfile.lock'
+
+# RSpec
+
+require 'rspec/core/rake_task'
+
+RSpec::Core::RakeTask.new do
+  if RUBY_PLATFORM == 'java'
+    ENV['JAVA_OPTS'] = '-Djdk.io.File.enableADS=true'
+    ENV['JRUBY_OPTS'] = '--debug'
+    ENV['COV_NO_FAIL'] = 'TRUE'
+  end
+  ENV['COV_SHOW_UNCOVERED'] = 'TRUE'
+end
+
+CLEAN << 'coverage'
+CLEAN << '.rspec_status'
+CLEAN << 'rspec-report.xml'
+
+# Rubocop
+
+require 'rubocop/rake_task'
+
+RuboCop::RakeTask.new do |t|
+  t.options = %w[
+    --format progress
+    --format json --out rubocop-report.json
+  ]
+end
+
+CLEAN << 'rubocop-report.json'
+
+unless RUBY_PLATFORM == 'java'
+  # yard:build
+
+  require 'yard'
+
+  YARD::Rake::YardocTask.new('yard:build') do |t|
+    t.files = %w[lib/**/*.rb examples/**/*]
+    t.stats_options = ['--list-undoc']
+  end
+
+  CLEAN << '.yardoc'
+  CLEAN << 'doc'
+
+  # yard:audit
+
+  desc 'Run yardstick to show missing YARD doc elements'
+  task :'yard:audit' do
+    sh "yardstick 'lib/**/*.rb'"
+  end
+
+  # yard:coverage
+
+  require 'yardstick/rake/verify'
+
+  Yardstick::Rake::Verify.new(:'yard:coverage') do |verify|
+    verify.threshold = 100
+  end
+
+  # yard
+
+  task yard: %i[yard:build yard:audit yard:coverage]
+end

data/exe/gem-version-boss

@@ -0,0 +1,6 @@
+#!/usr/bin/env ruby
+# frozen_string_literal: true
+
+require 'version_boss'
+
+VersionBoss::Gem::CommandLine.start(ARGV)