Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version_gem 1.1.4 → 1.1.6 (patch) #40

Merged
merged 1 commit into from
Feb 28, 2025

Conversation

depfu[bot]
Copy link

@depfu depfu bot commented Feb 25, 2025

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ version_gem (1.1.4 → 1.1.6) · Repo · Changelog

Release Notes

1.1.6 (from changelog)

  • 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 (from changelog)

  • 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)

Does any of this look wrong? Please let us know.


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 25, 2025
@pboling pboling merged commit 9e66cb7 into main Feb 28, 2025
6 of 7 checks passed
@depfu depfu bot deleted the depfu/update/version_gem-1.1.6 branch February 28, 2025 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant