version_gem 1.1.15

v1.1.15

on Ruby Gems

1.1.15 - 2026-08-01

• TAG: v1.1.15
• COVERAGE: 100.00% -- 119/119 lines in 8 files
• BRANCH COVERAGE: 100.00% -- 4/4 branches in 8 files
• 92.59% documented

Changed

• kettle-jem-template-20260716-001 - Shim gemspec manifests now include
  LICENSE.md instead of nonexistent LICENSE.txt.

• kettle-jem-template-20260716-002 - Generated gemspec manifests now ship fewer
  repository-only files by default to reduce downstream distro packaging churn.

• kettle-jem-template-20260720-002 - Development Gemfiles now use the released
  tree_sitter_language_pack gem 1.13.3 or newer by default.

• kettle-jem-template-20260725-002 - Version specs now use anonymous_loader to
  cover version.rb without redefining constants, or are removed when version
  specs are not managed for the project.

• kettle-jem-template-20260728-001 - Generated Ruby workflows now use clearer
  setup-ruby-flash planning and can prepare appraisal-only jobs without
  installing the main Gemfile bundle.

Added

• kettle-jem-template-20260720-001 - READMEs can now display configured
  corporate sponsor logos.
• kettle-jem-template-20260720-005 - README Support & Community links now
  include RubyForum.
• kettle-jem-template-20260726-001 - Projects now include YARD lint
  configuration and documentation dependencies so documentation issues fail
  before generated docs are refreshed.
• kettle-jem-template-20260727-001 - Spec harness documentation now lists the
  RSpec helpers provided by kettle-test.
• kettle-jem-template-20260729-005 - Gemspec metadata now publishes this
  project's RubyForum tag as mailing_list_uri, and support docs link to the
  tagged RubyForum community alongside Discord.

Fixed

• kettle-jem-template-20260720-003 - StructuredMerge Git diff driver config now
  uses the installed smorg-rb driver command.
• kettle-jem-template-20260720-004 - MRI-only projects now omit JRuby and
  TruffleRuby workflow jobs.
• kettle-jem-template-20260725-001 - Release pull request branches beginning
  with feature/release now run JRuby and TruffleRuby workflows.
• kettle-jem-template-20260726-002 - Generated version files now document their
  version namespace and constants, reducing warning-only YARD lint output.
• kettle-jem-template-20260726-003 - Coverage upload steps now treat Coveralls,
  QLTY, and Codecov as optional, so provider outages do not fail CI when local
  coverage thresholds still pass.
• kettle-jem-template-20260728-002 - Generated RuboCop configs now ignore the
  same gemfiles/vendor/bundle tree as .gitignore, so vendored dependency
  installs are not reported as project lint debt.
• kettle-jem-template-20260728-003 - Generated dep-heads workflows now run
  TruffleRuby jobs with current RubyGems and Bundler, avoiding setup failures
  before the test suite starts.
• kettle-jem-template-20260728-004 - Generated dep-heads workflows now use the
  setup-ruby Bundler install path for direct appraisal Gemfiles, avoiding rv
  lockfile parser failures on Git and path dependencies.
• kettle-jem-template-20260728-005 - VersionGem bootstrap now creates the
  missing canonical version spec when a project only has shim namespace version
  specs.
• kettle-jem-template-20260729-001 - Generated JRuby 9.4 workflows now use the
  legacy manual bundle install path, avoiding setup-time Bundler full-index
  failures against gem.coop.
• kettle-jem-template-20260729-002 - VersionGem bootstrap now preserves
  and templates dedicated version_gem.rb entrypoints even when the gemspec
  dependency is intentionally omitted, and generated anonymous-loader specs
  cover both version.rb and version_gem.rb.
• kettle-jem-template-20260729-003 - Old-Ruby gems below the VersionGem runtime
  floor now get managed minimal version.rb files and anonymous-loader version
  specs without adding version_gem.
• kettle-jem-template-20260730-001 - Gemspec package file enumeration now runs
  relative to the gemspec directory, so release package contents stay correct
  even when the gemspec is loaded from another working directory.

Community support 👉️

Many paths lead to being a sponsor or a backer of this project. Are you on such a path?