Gemfile: Update to Good Job 4.x#25
Merged
Merged
Conversation
awilfox
requested review from
anarchivist,
davezuckerman,
jason-raitz and
yzhoubk
awilfox
force-pushed
the
awilfox/AP-270-gj4
branch
from
1add3c6 to
98e89a8
Compare
Member
Author
|
v2: Rebased against current |
davezuckerman
approved these changes
Feb 19, 2026
Production console shows that we are `v4_ready?`, so let's go for it. This includes additional database migrations for v4 features. Ref: AP-270
awilfox
force-pushed
the
awilfox/AP-270-gj4
branch
from
98e89a8 to
264813f
Compare
Member
Author
|
v3: rebase against current |
yzhoubk
approved these changes
Feb 20, 2026
yzhoubk
left a comment
yzhoubk
left a comment
Contributor
There was a problem hiding this comment.
Great job, I tested a batch load job, everything looks good.
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
4 participants
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.
Production console shows that we are
v4_ready?, so let's go for it. This includes additional database migrations for v4 features.Ref: AP-270