version_gem

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning, and yes, platform and engine support are part of the public API. Please file a bug if you notice a violation of semantic versioning.

Unreleased

Added

Changed

Deprecated

Removed

Fixed

logo at top of README.md

Security

1.1.9 - 2025-09-02

TAG: v1.1.9
COVERAGE: 100.00% – 118/118 lines in 8 files
BRANCH COVERAGE: 100.00% – 4/4 branches in 8 files
84.62% documented

Added

re-templated gem using kettle-dev v1.1.2
- new binstubs for changelog, readme, commit message, & release management
- new CI workflows
- enhanced project documentation
More RBS types
docs site: https://version-gem.galtzo.com

Fixed

RBS types are more accurate

1.1.8 2025-05-06

TAG: 1.1.8
COVERAGE: 100.00% – 118/118 lines in 8 files
BRANCH COVERAGE: 100.00% – 4/4 branches in 8 files
84.62% documented

Added

CITATION.cff (@pboling)
Cryptographically signed with new 20-year cert (@pboling)
- expires 2045-04-29
Improved documentation (@pboling)
Addressed entire REEK list (@pboling)
GitLab CI, as an addition to existing GHA (@pboling)

1.1.7 2025-04-15

TAG: 1.1.7
Line Coverage: 100.0% (117 / 117)
Branch Coverage: 100.0% (4 / 4)
76.92% documented

Added

Support for Epoch Semantic Versioning (@pboling)
- extend VersionGem::Epoch in your library’s MyLib::Version module
Support for JRuby 10 (@pboling)
More documentation (@pboling)

Removed

Ruby 2.2 removed from CI, though technically still supported
- can’t run directly in GHA anymore

1.1.6 2025-02-24

TAG: 1.1.6
Line Coverage: 100.0% (77 / 77)
Branch Coverage: 100.0% (2 / 2)
77.78% documented

Added

Support for JRuby 9.1, 9.2, 9.3, 9.4, and head (@pboling)
Support for Truffle Ruby 22.3, 23.0, 23.1, 24.1, and head (@pboling)
Evergreen current latest engine release workflow (@pboling)
- Runs ruby, truffleruby, and jruby, always latest release
Improved developer experience for contributors (@pboling)
More documentation (@pboling)
Switch to stone_checksums for checksum generation (@pboling)

Changed

Code of Conduct updated - Contributor Covenant v2.0 => v2.1 (@pboling)

1.1.5 2025-02-22

TAG: 1.1.5
Line Coverage: 100.0% (77 / 77)
Branch Coverage: 100.0% (2 / 2)
77.78% documented

Added

Document approach to get code coverage on your gem’s version.rb file (@pboling)
More documentation, and yard task for documentation (@pboling)
Documentation of Ruby version and SemVer support (@pboling)

Fixed

#3 - Allow packaging without signing (@pboling)
- to support secure linux distros which have alternate means of signing packages within their package managers
Code coverage tracking (@pboling)
Documentation of usage in gemspec via Kernel.load (@pboling)
Improved gemspec config (@pboling)

1.1.4 2024-03-21

TAG: 1.1.4

Added

Ruby 3.3 to CI (@pboling)

Fixed

Remove the executable bit from non-executable files (@Fryguy)

1.1.3 2023-06-05

TAG: 1.1.3

Added

More test coverage (now 100% 🎉) (@pboling)
Improved documentation (now 77% 🎉) (@pboling)
Gemfile context pattern (@pboling)
Improved linting (via rubocop-lts) (@pboling)
More robust GHA config (@pboling)
(dev) Dependencies (@pboling)
- yard-junk
- redcarpet
- pry, IRB alternative
- pry-suite
- debase, for IDE debugging
(dev) Rake task for rubocop_gradual (@pboling)

Fixed

(dev) yard documentation task (@pboling)

Removed

Formally drop Ruby 2.2 support
- Ruby 2.2 was already de facto minimum version supported, which is why this wasn’t a 2.0 release.

1.1.2 - 2023-03-17

TAG: 1.1.2

Added

VersionGem::Ruby to help library CI integration against many different versions of Ruby (@pboling)
- Experimental, optional, require (not loaded by default, which is why this can be in a patch)
Spec coverage is now 100%, lines and branches, including the fabled version.rb (@pboling)
Full RBS Signatures (@pboling)

1.1.1 - 2022-09-19

TAG: 1.1.1

Added

Alternatives section to README.md (@pboling)
Signing cert for gem releases (@pboling)
Mailing List and other metadata URIs (@pboling)
Checksums for released gems (@pboling)

Changed

SECURITY.md policy (@pboling)
Version methods are now memoized ( =) on initial call for performance (@pboling)
Gem releases are now cryptographically signed (@pboling)