[ruby] Update good_job 4.16.0 → 4.18.1 (minor)#1498
Merged
depfu[bot] merged 1 commit intomainfrom Apr 19, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ good_job (4.16.0 → 4.18.1) · Repo · Changelog
Release Notes
4.18.1
4.18.0
4.17.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 17 commits:
Release good_job v4.18.1Make job lifecycle methods lock-strategy-aware (#1756)Fix concurrent PG connection access in ProcessHeartbeat#refresh_process (#1755)Release good_job v4.18.0Replace AR attributes API with explicit accessors; add breaking migration spec (#1753)Make bulk action buttons responsive to job state filter (#1751)Introduce GoodJob::InterruptedError string for interrupted execution records (#1750)Fix dashboard pagination omitting jobs created in the same second (#1749)Add GoodJob.handled_exceptions configuration with NotImplementedError default (#1748)Document initializer workaround for deferred autoloading in development (#1747)Allow adding the currently executing job to a batch (#1746)Show enabled/paused split badge for cron schedules in navbar and table (#1744)Release good_job v4.17.0Introduce advisory lock key customization support methods (#1722)Convert UI JavaScript modules to Stimulus controllers (#1743)Strip pg_catalog namespace from enable_extension in schema.rb (#1742)Use system tmpdir for generator spec example app to avoid bin/rails rename (#1740)Commits
See the full diff on Github. The new version differs by 14 commits:
Bump version to v4.1.2 (#529)Update dtoa to version from Ruby 4.0 (#528)Merge pull request #526 from ruby/dependabot/github_actions/step-security/harden-runner-2.17.0Bump step-security/harden-runner from 2.16.1 to 2.17.0Fix unary minus on unsigned type warning (#525)BigMath.exp overflow/underflow check (#523)Revert "Add a workaround for slow BigDecimal#to_f when it has large N_significant_digits (#514)" (#522)Use '0'+n for converting single digit to char (#521)Merge pull request #517 from ruby/dependabot/github_actions/rubygems/release-gem-1.2.0Merge pull request #518 from ruby/dependabot/github_actions/step-security/harden-runner-2.16.1Fix calloc-transposed-args warning (#520)Optimize BigDecimal#to_s (#519)Bump step-security/harden-runner from 2.16.0 to 2.16.1Bump rubygems/release-gem from 1.1.4 to 1.2.0Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Release Notes
13.4.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 4 commits:
v13.4.2Merge pull request #723 from ruby/fix/testopts-preserve-existing-valueIsolate TESTOPTS env in TestRakeTestTask setup/teardownPreserve ENV["TESTOPTS"] when verbose is enabledDepfu 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